[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3917C05D9F83184EAA45CE249FF1B1DD0266FC80@SHSMSX103.ccr.corp.intel.com>
Date: Mon, 29 Dec 2014 01:33:37 +0000
From: "Ma, Xindong" <xindong.ma@...el.com>
To: Al Viro <viro@...IV.linux.org.uk>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"oleg@...hat.com" <oleg@...hat.com>,
"mhocko@...e.cz" <mhocko@...e.cz>,
"mingo@...nel.org" <mingo@...nel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"riel@...hat.com" <riel@...hat.com>,
"ionut.m.alexa@...il.com" <ionut.m.alexa@...il.com>,
"peter@...leysoftware.com" <peter@...leysoftware.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Zhang, Di" <di.zhang@...el.com>,
"Sun, Zhonghua" <zhonghua.sun@...el.com>
Subject: RE: [PATCH] move exit_task_work() before exit_fs().
> On Fri, Dec 26, 2014 at 03:45:25PM +0800, Leon Ma wrote:
> > We encountered following panic. The scenario is the process is exiting
> > and executing its task work. When closing dev node, the driver
> > triggers a firmware reload according to device status. Because task->fs is
> set to NULL in exit_fs(), panic happens.
> > Task work is a common interface, we should not limite the resource the
> user will utilize.
>
> Fix your driver. Forget ->fs being NULL; what will happen if your process is
> chrooted?
Thanks, But I'm not clear what is the limitation added to chroot env?
--
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