[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140630201741.GA20853@htj.dyndns.org>
Date: Mon, 30 Jun 2014 16:17:41 -0400
From: Tejun Heo <tj@...nel.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Christoph Hellwig <hch@....de>,
Josh Boyer <jwboyer@...oraproject.org>,
Rusty Russell <rusty@...tcorp.com.au>,
virtualization@...ts.linux-foundation.org,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Brian Lane <bcl@...hat.com>,
John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>,
Eric Paris <eparis@...isplace.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: virt_blk BUG: sleeping function called from invalid context
On Sun, Jun 29, 2014 at 02:55:36PM -0600, Jens Axboe wrote:
> > commit d911d98748018f7c8facc035ba39c30f5cce6f9c
> > Author: Tejun Heo <tj@...nel.org>
> > Date: Wed Apr 9 11:07:31 2014 -0400
> >
> > kernfs: make kernfs_notify() trigger inotify events too
> >
> > Tejun, what do you think?
> >
> > Josh, Brian, could you try reverting that commit to see if it helps?
>
> That definitely be a bug. If you need to block off ->bi_end_io(), just
> must punt to a worker thread.
Ugh... didn't realize we had users triggering sysfs notifications from
an atomic context. fsnotify support requires sleepable context.
Guess I'll have to punt it to a work item. :(
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists