LKML Archive on
help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <>
To: Nick Piggin <>
Subject: Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
Date: Tue, 28 Oct 2008 22:38:30 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Nick Piggin wrote:
> On Saturday 25 October 2008 03:10, Vladislav Bolkhovitin wrote:
>> Hi,
>> During recent debugging session of my SCSI target SCST
>> ( I noticed many
>> WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
>> messages in kernel log on the initiator. I attached the full log of
>> several of them.
>> My target was buggy and I was working on fixing it, but I suppose Linux
>> should handle such failures more gracefully. In all the cases the target
>> had one type of failure: it "ate" a SCSI command and never returned
>> result of it.
> Right. This is one of the warnings I see in my fault-injection testing.
> It is fixed by my patch to clean up and improve the page and buffer
> error handling in the vm/fs.

Can you specify which patch you referring? Is it in 2.6.27?

  reply	other threads:[~2008-10-28 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 16:10 Vladislav Bolkhovitin
2008-10-28 12:42 ` Nick Piggin
2008-10-28 19:38   ` Vladislav Bolkhovitin [this message]
2008-10-29  0:25     ` Nick Piggin
2008-10-31 18:11       ` Vladislav Bolkhovitin
2008-11-01 13:08         ` FS corruption after I/O errors Vladislav Bolkhovitin
2008-11-06 10:48         ` WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66() Nick Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).