From: Ben Hutchings <ben@decadent.org.uk>
To: Michal Hocko <mhocko@kernel.org>,
"Jorgen S. Hansen" <jhansen@vmware.com>
Cc: Aditya Sarwade <asarwade@vmware.com>,
Thomas Hellstrom <thellstrom@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Masik Petr <Petr.Masik@nudz.cz>,
Sasha Levin <alexander.levin@verizon.com>,
Stable tree <stable@vger.kernel.org>
Subject: Re: scheduling while atomic from vmci_transport_recv_stream_cb in 3.16 kernels
Date: Tue, 21 Nov 2017 19:58:13 +0000 [thread overview]
Message-ID: <1511294293.2841.0.camel@decadent.org.uk> (raw)
In-Reply-To: <20170913151939.gf7n6rvvjtz47tz7@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Wed, 2017-09-13 at 17:19 +0200, Michal Hocko wrote:
> On Wed 13-09-17 15:07:26, Jorgen S. Hansen wrote:
[...]
> > The patch below has been used to fix the above issue by other distros
> > - among them Redhat for the 3.10 kernel, so it should work for 3.16 as
> > well.
>
> Thanks for the confirmation. I do not see 4ef7ea9195ea ("VSOCK: sock_put
> wasn't safe to call in interrupt context") in 3.10 stable branch
> though.
>
> > In addition to the patch above, there are two other patches that
> > need to be applied on top for the fix to be correct:
> >
> > 8566b86ab9f0f45bc6f7dd422b21de9d0cf5415a "VSOCK: Fix lockdep issue."
> >
> > and
> >
> > 8ab18d71de8b07d2c4d6f984b718418c09ea45c5 "VSOCK: Detach QP check should filter out non matching QPs."
>
> Good to know. I will send all three patches cherry-picked on top of the
> current 3.16 stable branch. Could you have a look please?
I've now queued these all up.
Ben.
--
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-21 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 9:08 scheduling while atomic from vmci_transport_recv_stream_cb in 3.16 kernels Michal Hocko
2017-09-13 15:07 ` Jorgen S. Hansen
2017-09-13 15:19 ` Michal Hocko
2017-09-13 15:23 ` [PATCH stable-3.16 1/3] VSOCK: sock_put wasn't safe to call in interrupt context Michal Hocko
2017-09-13 15:23 ` [PATCH stable-3.16 2/3] VSOCK: Fix lockdep issue Michal Hocko
2017-09-13 15:23 ` [PATCH stable-3.16 3/3] VSOCK: Detach QP check should filter out non matching QPs Michal Hocko
2017-09-13 18:58 ` scheduling while atomic from vmci_transport_recv_stream_cb in 3.16 kernels Jorgen S. Hansen
2017-09-14 8:59 ` Michal Hocko
2017-09-15 17:12 ` Ben Hutchings
2017-09-18 6:11 ` Michal Hocko
2017-11-21 19:58 ` Ben Hutchings [this message]
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=1511294293.2841.0.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Petr.Masik@nudz.cz \
--cc=alexander.levin@verizon.com \
--cc=asarwade@vmware.com \
--cc=jhansen@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=thellstrom@vmware.com \
/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