From: Mike Snitzer <snitzer@redhat.com>
To: Minfei Huang <mnghuan@gmail.com>
Cc: agk@redhat.com, shli@kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESENT] dm: Check kthread_run's return value
Date: Wed, 6 Jul 2016 09:31:29 -0400 [thread overview]
Message-ID: <20160706133129.GB28379@redhat.com> (raw)
In-Reply-To: <20160706132755.GA1712@MinfeideMacBook-Pro.local>
On Wed, Jul 06 2016 at 9:27am -0400,
Minfei Huang <mnghuan@gmail.com> wrote:
> On 07/06/16 at 09:16P, Mike Snitzer wrote:
> > On Mon, Jul 04 2016 at 11:25am -0400,
> > Minfei Huang <mnghuan@gmail.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@gmail.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.
Given the code movement it isn't easy to do (by simply adding a stable@
cc). I've not seen a single report of an ignored kthread_run() failure
for multipath using .request_fn interface.
next prev parent reply other threads:[~2016-07-06 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 15:25 [PATCH RESENT] dm: Check kthread_run's return value Minfei Huang
2016-07-06 13:16 ` Mike Snitzer
2016-07-06 13:27 ` Minfei Huang
2016-07-06 13:31 ` Mike Snitzer [this message]
2016-07-06 13:38 ` Minfei Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160706133129.GB28379@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mnghuan@gmail.com \
--cc=shli@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).