[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 12 Dec 2013 00:53:33 +0000
From: "Liu, Chuansheng" <chuansheng.liu@...el.com>
To: Miklos Szeredi <miklos@...redi.hu>
CC: "mszeredi@...e.cz" <mszeredi@...e.cz>,
"fuse-devel@...ts.sourceforge.net" <fuse-devel@...ts.sourceforge.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [fuse-devel] fuse try to freeze with lock held
Hello Miklos,
> -----Original Message-----
> From: Miklos Szeredi [mailto:miklos@...redi.hu]
> Sent: Wednesday, December 11, 2013 11:35 PM
> To: Liu, Chuansheng
> Cc: mszeredi@...e.cz; fuse-devel@...ts.sourceforge.net;
> linux-kernel@...r.kernel.org
> Subject: Re: [fuse-devel] fuse try to freeze with lock held
>
> On Wed, Nov 27, 2013 at 3:19 AM, Liu, Chuansheng
> <chuansheng.liu@...el.com> wrote:
> > Hit the below warning when enabling the CONFIG_DEBUG_LOCK_ALLOC,
> > __fuse_request_send == >
> > request_wait_answer == >
> > wait_event_freezable == >
> > try_to_freeze()
> >
> > But here the inode->i_mutex is hold yet in vfs_readdir().
> >
> > Could anyone give some help? Thanks.
> >
>
> Mainline doesn't have wait_event_freezable() in fuse. What kernel
> variant is this?
>
Thanks your pointing out, it is my fault since it is not mainline.
Powered by blists - more mailing lists