Re: kernel BUG at fs/ext4/fsync.c:LINE!

On Fri, Sep 15, 2017 at 12:41 AM, Andreas Dilger wrote: > I don't think a reproducer is needed. It looks like the fsync callpath > is happening from an IRQ context due to IO completion, and then re-entering > the filesystem while a transaction is already started. It looks

Re: kernel BUG at fs/ext4/fsync.c:LINE!

On Fri, Sep 15, 2017 at 12:41 AM, Andreas Dilger wrote: > I don't think a reproducer is needed. It looks like the fsync callpath > is happening from an IRQ context due to IO completion, and then re-entering > the filesystem while a transaction is already started. It looks like the > original IO

Re: kernel BUG at fs/ext4/fsync.c:LINE!

On Sep 14, 2017, at 9:04 AM, ChunYu Wang wrote: > > Hi GeneBlue, > > Thanks for this reporting, do you have any logs related to the bug and > could find the syscalls enabled for fuzzing during triggering this > bug? I do not think it is not reproducible, but first, it needs

Re: kernel BUG at fs/ext4/fsync.c:LINE!

On Sep 14, 2017, at 9:04 AM, ChunYu Wang wrote: > > Hi GeneBlue, > > Thanks for this reporting, do you have any logs related to the bug and > could find the syscalls enabled for fuzzing during triggering this > bug? I do not think it is not reproducible, but first, it needs some > inspections

Re: kernel BUG at fs/ext4/fsync.c:LINE!

Hi GeneBlue, Thanks for this reporting, do you have any logs related to the bug and could find the syscalls enabled for fuzzing during triggering this bug? I do not think it is not reproducible, but first, it needs some inspections manually. - ChunYu On Thu, Sep 14, 2017 at 7:54 PM, GeneBlue

Re: kernel BUG at fs/ext4/fsync.c:LINE!

Hi GeneBlue, Thanks for this reporting, do you have any logs related to the bug and could find the syscalls enabled for fuzzing during triggering this bug? I do not think it is not reproducible, but first, it needs some inspections manually. - ChunYu On Thu, Sep 14, 2017 at 7:54 PM, GeneBlue