Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-12-19 Thread Ming Lei
Hi, On Thu, Dec 8, 2016 at 11:57 PM, Ming Lei wrote: > Hi, > > On Mon, Nov 28, 2016 at 9:40 PM, Jeff Layton wrote: >> On Mon, 2016-11-28 at 11:10 +0800, Ming Lei wrote: >>> Hi Guys, >>> >>> When I run stress-ng via the following steps on one ARM64 dual >>> socket system(Cavium Thunder), the kern

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-12-08 Thread Ming Lei
Hi, On Mon, Nov 28, 2016 at 9:40 PM, Jeff Layton wrote: > On Mon, 2016-11-28 at 11:10 +0800, Ming Lei wrote: >> Hi Guys, >> >> When I run stress-ng via the following steps on one ARM64 dual >> socket system(Cavium Thunder), the kernel oops[1] can often be >> triggered after running the stress tes

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-12-06 Thread Ming Lei
Hi Will, On Thu, Dec 1, 2016 at 7:30 PM, Will Deacon wrote: > On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: >> When I run stress-ng via the following steps on one ARM64 dual >> socket system(Cavium Thunder), the kernel oops[1] can often be >> triggered after running the stress test fo

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-12-01 Thread Will Deacon
On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: > When I run stress-ng via the following steps on one ARM64 dual > socket system(Cavium Thunder), the kernel oops[1] can often be > triggered after running the stress test for several hours(sometimes > it may take longer): > > - git clone g

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-11-28 Thread Ming Lei
Hi Jeff, On Mon, Nov 28, 2016 at 9:40 PM, Jeff Layton wrote: > On Mon, 2016-11-28 at 11:10 +0800, Ming Lei wrote: >> Hi Guys, >> >> When I run stress-ng via the following steps on one ARM64 dual >> socket system(Cavium Thunder), the kernel oops[1] can often be >> triggered after running the stres

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-11-28 Thread Jeff Layton
On Mon, 2016-11-28 at 11:10 +0800, Ming Lei wrote: > Hi Guys, > > When I run stress-ng via the following steps on one ARM64 dual > socket system(Cavium Thunder), the kernel oops[1] can often be > triggered after running the stress test for several hours(sometimes > it may take longer): > > - git

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-11-28 Thread Ming Lei
Hi Will, On Mon, Nov 28, 2016 at 6:52 PM, Will Deacon wrote: > Hi Ming, > > On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: >> When I run stress-ng via the following steps on one ARM64 dual >> socket system(Cavium Thunder), the kernel oops[1] can often be >> triggered after running the

Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-11-28 Thread Will Deacon
Hi Ming, On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: > When I run stress-ng via the following steps on one ARM64 dual > socket system(Cavium Thunder), the kernel oops[1] can often be > triggered after running the stress test for several hours(sometimes > it may take longer): > > - g

[bug report v4.8] fs/locks.c: kernel oops during posix lock stress test

2016-11-27 Thread Ming Lei
Hi Guys, When I run stress-ng via the following steps on one ARM64 dual socket system(Cavium Thunder), the kernel oops[1] can often be triggered after running the stress test for several hours(sometimes it may take longer): - git clone git://kernel.ubuntu.com/cking/stress-ng.git - apply the attac