Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 05:44:22PM +0100, Mel Gorman wrote: > On Tue, Aug 08, 2017 at 09:06:48AM -0700, Linus Torvalds wrote: > > On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > > > > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > > > and

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 05:44:22PM +0100, Mel Gorman wrote: > On Tue, Aug 08, 2017 at 09:06:48AM -0700, Linus Torvalds wrote: > > On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > > > > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > > > and everything else seems

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mel Gorman
On Tue, Aug 08, 2017 at 09:06:48AM -0700, Linus Torvalds wrote: > On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > > and everything else seems fine. I'll have a go with additional debug > >

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mel Gorman
On Tue, Aug 08, 2017 at 09:06:48AM -0700, Linus Torvalds wrote: > On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > > and everything else seems fine. I'll have a go with additional debug > > enabled just in case. >

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Linus Torvalds
On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > and everything else seems fine. I'll have a go with additional debug > enabled just in case. Ok, great, a - mostly - false alarm. I do wonder if

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Linus Torvalds
On Tue, Aug 8, 2017 at 8:41 AM, Mark Rutland wrote: > > With my __BUG_FLAGS() issue corrected, the WARN_ON_ONCE() fires once, > and everything else seems fine. I'll have a go with additional debug > enabled just in case. Ok, great, a - mostly - false alarm. I do wonder if we should just remove

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 04:32:30PM +0100, Mel Gorman wrote: > On Tue, Aug 08, 2017 at 11:52:05AM +0100, Mark Rutland wrote: > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > > major, and so far I

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 04:32:30PM +0100, Mel Gorman wrote: > On Tue, Aug 08, 2017 at 11:52:05AM +0100, Mark Rutland wrote: > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > > major, and so far I

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mel Gorman
On Tue, Aug 08, 2017 at 11:52:05AM +0100, Mark Rutland wrote: > Hi, > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > major, and so far I haven't had any luck reproducing this, so it may be > an

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mel Gorman
On Tue, Aug 08, 2017 at 11:52:05AM +0100, Mark Rutland wrote: > Hi, > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > major, and so far I haven't had any luck reproducing this, so it may be > an

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 03:57:32PM +0100, Mark Rutland wrote: > The below test case fires for me in a few seconds on an arm64 platform, > triggering the kernel BUG at kernel/futex.c:679. If left running for longer, I > then get a stream of other BUGs that I believe are a result of the first >

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 03:57:32PM +0100, Mark Rutland wrote: > The below test case fires for me in a few seconds on an arm64 platform, > triggering the kernel BUG at kernel/futex.c:679. If left running for longer, I > then get a stream of other BUGs that I believe are a result of the first >

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 11:52:04AM +0100, Mark Rutland wrote: > Hi, > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > major, and so far I haven't had any luck reproducing this, so it may be > an

Re: kernel BUG at kernel/futex.c:679 on v4.13-rc3-ish on arm64

2017-08-08 Thread Mark Rutland
On Tue, Aug 08, 2017 at 11:52:04AM +0100, Mark Rutland wrote: > Hi, > > As a heads-up, I hit the below splat when using Syzkaller to fuzz arm64 > VMAP_STACK patches [1] atop of v4.13-rc3. I haven't hit anything else > major, and so far I haven't had any luck reproducing this, so it may be > an