Bug#696650: fsync() on read-only RAID triggers BUG

2013-01-27 Thread Christoph Hellwig
On Sat, Jan 26, 2013 at 07:44:40PM +, 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. -- To

Bug#696650: fsync() on read-only RAID triggers BUG

2013-01-26 Thread Ben Hutchings
On Fri, 2013-01-25 at 16:09 +0100, Sebastian Riemer wrote: > On 20.01.2013 19:44, Ben Hutchings wrote: > > # Call fsync() > > python -c "import os; os.fsync(os.open('/dev/md0', os.O_RDWR))" > > --- END --- > > > > I assume that the sync request should be filtered out at some point > > before this

Bug#696650: fsync() on read-only RAID triggers BUG

2013-01-20 Thread Ben Hutchings
We've had a report of the BUG in md_write_start() being triggered while running the Debian installer: . Based on the call trace, I came up with the following script that reproduces this under Linux 3.2.35 and 3.7.3: --- BEGIN --- #!/bin/bash -ex # Set up temporary R