[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160706132755.GA1712@MinfeideMacBook-Pro.local>
Date: Wed, 6 Jul 2016 21:27:55 +0800
From: Minfei Huang <mnghuan@...il.com>
To: Mike Snitzer <snitzer@...hat.com>
Cc: agk@...hat.com, shli@...nel.org, dm-devel@...hat.com,
linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESENT] dm: Check kthread_run's return value
On 07/06/16 at 09:16P, Mike Snitzer wrote:
> On Mon, Jul 04 2016 at 11:25am -0400,
> Minfei Huang <mnghuan@...il.com> wrote:
>
> > kthread function is used to process kthread_work. And there is no return
> > value checking during create this thread. Add this checking to fix this
> > issue.
> >
> > Signed-off-by: Minfei Huang <mnghuan@...il.com>
> This needed rebasing against linux-dm.git's 'for-next'. I've now staged
> this fix for 4.8 inclusion, see:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=7193a9defcab6f3d3f1eb64c68bad7534e5a39ad
Seems that we should fix it in stable as well.
Thanks
Minfei
Powered by blists - more mailing lists