Re: WARNING in up_write

2018-09-04 Thread Dmitry Vyukov
On Thu, Apr 5, 2018 at 10:22 AM, Dmitry Vyukov wrote: > On Thu, Apr 5, 2018 at 5:24 AM, Matthew Wilcox wrote: >> On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: >>> On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: >>> > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dm

Re: WARNING in up_write

2018-04-13 Thread Dmitry Vyukov
On Fri, Apr 6, 2018 at 4:01 AM, Dave Chinner wrote: > On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: >> On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: >> > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: >> > > On Wed, Apr 04, 2018 at 11:22:00PM -0400,

Re: WARNING in up_write

2018-04-05 Thread Dave Chinner
On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: > On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: > > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: > > > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > > > > On Wed, Apr 04, 2018 at 1

Re: WARNING in up_write

2018-04-05 Thread Theodore Y. Ts'o
On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: > Well, ultimately a human needed to investigate the syzbot bug report to figure > out what was really going on. In my view, the largest problem is that there > are > simply too many bugs, so many are getting ignored. If there were on

Re: WARNING in up_write

2018-04-05 Thread Eric Biggers
On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: > > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > > > On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: > > > > On Wed, Apr 04, 2018 at

Re: WARNING in up_write

2018-04-05 Thread Dave Chinner
On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > > On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: > > > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: > > > > On Tue, Apr 3, 2018 at

Re: WARNING in up_write

2018-04-05 Thread Dmitry Vyukov
On Thu, Apr 5, 2018 at 5:24 AM, Matthew Wilcox wrote: > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: >> On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: >> > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: >> > > On Tue, Apr 3, 2018 at 4:01 AM, sy

Re: WARNING in up_write

2018-04-04 Thread Matthew Wilcox
On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: > > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: > > > On Tue, Apr 3, 2018 at 4:01 AM, syzbot > > > wrote: > > > > DEBUG_LOCKS_WARN_ON(sem->owner !=

Re: WARNING in up_write

2018-04-04 Thread Theodore Y. Ts'o
On Wed, Apr 04, 2018 at 12:35:04PM -0700, Matthew Wilcox wrote: > On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: > > On Tue, Apr 3, 2018 at 4:01 AM, syzbot > > wrote: > > > DEBUG_LOCKS_WARN_ON(sem->owner != get_current()) > > > WARNING: CPU: 1 PID: 4441 at kernel/locking/rwsem.c:13

Re: WARNING in up_write

2018-04-04 Thread Matthew Wilcox
On Wed, Apr 04, 2018 at 09:24:05PM +0200, Dmitry Vyukov wrote: > On Tue, Apr 3, 2018 at 4:01 AM, syzbot > wrote: > > DEBUG_LOCKS_WARN_ON(sem->owner != get_current()) > > WARNING: CPU: 1 PID: 4441 at kernel/locking/rwsem.c:133 up_write+0x1cc/0x210 > > kernel/locking/rwsem.c:133 > > Kernel panic - n

Re: WARNING in up_write

2018-04-04 Thread Dmitry Vyukov
On Tue, Apr 3, 2018 at 4:01 AM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 86bbbebac1933e6e95e8234c4f7d220c5ddd38bc (Mon Apr 2 18:47:07 2018 +) > Merge branch 'ras-core-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip > syzbot dashboard