Re: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002

2013-10-14 Thread Alessandro Rubini
Hello. > I'm getting the following with randconfig testing in kvm, config is > .attached. I acknowledge this is a bug of mine, and your .config shows your are testing v3.11. I posted the fix on Jul 16th 2013, and it is now in master as v3.11-rc2-11-g783c2fb. However it is not an ancestor of v3.

Re: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002

2013-10-14 Thread Borislav Petkov
On Mon, Oct 14, 2013 at 05:10:17PM +0200, Alessandro Rubini wrote: > Hello. > > > I'm getting the following with randconfig testing in kvm, config is > > .attached. > > I acknowledge this is a bug of mine, and your .config shows your are > testing v3.11. > > I posted the fix on Jul 16th 2013, an

Re: [fmc] BUG: scheduling while atomic: swapper/0/1/0x00000002

2013-08-12 Thread Fengguang Wu
On Mon, Aug 12, 2013 at 02:42:27PM +0200, Alessandro Rubini wrote: > > On 08/11/2013 09:52 PM, Fengguang Wu wrote: > >> FYI, the bug still exists in the upstream and linux-next kernels. > > Strange. Greg approved the patch I sent. I see it in next-20130809 > but also next-20130801 and other ones w

Re: [fmc] BUG: scheduling while atomic: swapper/0/1/0x00000002

2013-08-12 Thread Alessandro Rubini
> On 08/11/2013 09:52 PM, Fengguang Wu wrote: >> FYI, the bug still exists in the upstream and linux-next kernels. Strange. Greg approved the patch I sent. I see it in next-20130809 but also next-20130801 and other ones with the same hash: 783c2fb FMC: fix locking in sample chardev driver How

Re: [fmc] BUG: scheduling while atomic: swapper/0/1/0x00000002

2013-08-11 Thread yun wang
On 08/11/2013 09:52 PM, Fengguang Wu wrote: Alessandro, FYI, the bug still exists in the upstream and linux-next kernels. And it's caused by: fc_probe(...) { ... spin_lock(&fc_lock); ret = misc_register(&fc->misc); ...