Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
- Date: Tue, 28 Oct 2008 23:42:04 +1100
On Saturday 25 October 2008 03:10, Vladislav Bolkhovitin wrote:
Hi,
During recent debugging session of my SCSI target SCST
(http://scst.sf.net) 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- From: Vladislav Bolkhovitin
- Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- References:
- WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- From: Vladislav Bolkhovitin
- WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- Prev by Date: Re: [PATCH 2/3] Implement generic freeze feature
- Next by Date: Re: [PATCH 4/4][mmotm] memcg: simple migration handling
- Previous by thread: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- Next by thread: Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
- Index(es):
Relevant Pages
|
