Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()

On Wednesday 29 October 2008 06:38, Vladislav Bolkhovitin wrote:
Nick Piggin wrote:
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.

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

It's just an RFC at the moment which I posted to fsdevel. Not in 2.6.27.
--
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/

Relevant Pages

  • WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
    ... During recent debugging session of my SCSI target SCST I noticed many ... messages in kernel log on the initiator. ... My target was buggy and I was working on fixing it, but I suppose Linux should handle such failures more gracefully. ... Oct 16 21:59:05 inif kernel: Aborting journal on device sdf. ...
    (Linux-Kernel)
  • Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
    ... During recent debugging session of my SCSI target SCST ... messages in kernel log on the initiator. ... My target was buggy and I was working on fixing it, ... should handle such failures more gracefully. ...
    (Linux-Kernel)
  • Re: WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0x51/0x66()
    ... During recent debugging session of my SCSI target SCST ... messages in kernel log on the initiator. ... My target was buggy and I was working on fixing it, ... should handle such failures more gracefully. ...
    (Linux-Kernel)
  • [patch 02/73] dm: table detect io beyond device
    ... If anyone has any objections, ... Patch 512875bd9661368da6f993205a61213b79ba1df0 in mainline. ... outstanding I/O to the part of the device that is being removed. ... Allocate both the target array and offset array at once. ...
    (Linux-Kernel)
  • [RFC]: Support for zero-copy TCP transmit of user space data
    ... Recently I submitted a new SCSI target framework and 4 target drivers for it for the first iteration of review and comments. ... Patch, implementing this optimization was also sent in the patchset, see http://lkml.org/lkml/2008/12/10/296. ... Related kernel config option TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION should be disabled by default in general distro kernels, so the would be no harm at all from this patch. ... ISCSI-SCST can work without this patch or with TCP_ZERO_COPY_TRANSFER_COMPLETION_NOTIFICATION option disabled, although with user space device handlers it will work considerably worse. ...
    (Linux-Kernel)