Re: fsync() on read-only RAID triggers BUG

fsync() on read-only RAID triggers BUG · Ben Hutchings <hidden> · 2013-01-20
Re: fsync() on read-only RAID triggers BUG · Sebastian Riemer <hidden> · 2013-01-25
Re: fsync() on read-only RAID triggers BUG · Ben Hutchings <hidden> · 2013-01-26
Re: fsync() on read-only RAID triggers BUG · Christoph Hellwig <hch@infradead.org> · 2013-01-27
[PATCH v2] md: protect against crash upon fsync on ro array · Sebastian Riemer <hidden> · 2013-01-28
[PATCH v3] md: protect against crash upon fsync on ro array · Sebastian Riemer <hidden> · 2013-01-28
Re: [PATCH v3] md: protect against crash upon fsync on ro array · Ben Hutchings <hidden> · 2013-01-29
[PATCH v4] md: protect against crash upon fsync on ro array · Sebastian Riemer <hidden> · 2013-01-29
Re: [PATCH v5] md: protect against crash upon fsync on ro array · Paul Menzel <hidden> · 2013-01-29
Re: [PATCH v5] md: protect against crash upon fsync on ro array · Sebastian Riemer <hidden> · 2013-01-31
Re: [PATCH v5] md: protect against crash upon fsync on ro array · NeilBrown <hidden> · 2013-02-04

From: Christoph Hellwig <hch@infradead.org>
Date: 2013-01-27 16:39:42

On Sat, Jan 26, 2013 at 07:44:40PM +0000, Ben Hutchings wrote:

I applied this on top of 3.2.37 and it certainly fixes the crash.
However I wonder whether fsync() should fail or should immediately
succeed.  I don't know whether the installer expects it to succeed.

It should succeed.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help