linux-kernel - Re: WARNING: at fs/buffer.c:1186 mark_buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Oct 2008 23:42:04 +1100
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Vladislav Bolkhovitin <vst@...b.net>
Cc:	linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/