Re: shared/298 lockdep splat?

2017-09-26 Thread Byungchul Park
On Tue, Sep 26, 2017 at 01:51:49PM +1000, Dave Chinner wrote: > On Thu, Sep 21, 2017 at 05:47:14PM +0900, Byungchul Park wrote: > > On Thu, Sep 21, 2017 at 08:22:56AM +1000, Dave Chinner wrote: > > > Peter, this is the sort of false positive I mentioned were likely to > > > occur without some serio

Re: shared/298 lockdep splat?

2017-09-25 Thread Dave Chinner
On Thu, Sep 21, 2017 at 05:47:14PM +0900, Byungchul Park wrote: > On Thu, Sep 21, 2017 at 08:22:56AM +1000, Dave Chinner wrote: > > Peter, this is the sort of false positive I mentioned were likely to > > occur without some serious work to annotate the IO stack to prevent > > them. We can nest mul

Re: shared/298 lockdep splat?

2017-09-21 Thread Byungchul Park
On Thu, Sep 21, 2017 at 08:22:56AM +1000, Dave Chinner wrote: > > == > > WARNING: possible circular locking dependency detected > > 4.14.0-rc1-fixes #1 Tainted: GW > > -- > > loop0/

Re: shared/298 lockdep splat?

2017-09-20 Thread Dave Chinner
[cc lkml, PeterZ and Byungchul] On Wed, Sep 20, 2017 at 02:10:42PM -0700, Darrick J. Wong wrote: > Hello list, > > Yesterday I tried setting up qemu 2.10 with some (fake) nvdimms backed > by an on-disk file. Midway through a -g auto xfstests run, shared/298 > produced the attached dmesg spew. I