From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>, edumazet@google.com
Cc: netdev@vger.kernel.org, dsa@cumulusnetworks.com,
james.l.morris@oracle.com, casey@schaufler-ca.com
Subject: Re: [PATCH net 0/2] tcp: fix SELinux/Smack corruptions
Date: Sun, 03 Dec 2017 09:33:28 -0800 [thread overview]
Message-ID: <1512322408.19682.55.camel@gmail.com> (raw)
In-Reply-To: <20171203.104228.2271114416251083134.davem@davemloft.net>
On Sun, 2017-12-03 at 10:42 -0500, David Miller wrote:
> From: Eric Dumazet <edumazet@google.com>
> Date: Fri, 1 Dec 2017 15:08:11 -0800
>
> > James Morris reported kernel stack corruption bug that
> > we tracked back to commit 971f10eca186 ("tcp: better TCP_SKB_CB
> > layout to reduce cache line misses")
> >
> > First patch needs to be backported to kernels >= 3.18,
> > while second patch needs to be backported to kernels >= 4.9, since
> > this was the time when inet_exact_dif_match appeared.
>
> I don't know why but patch #2 never made it into patchwork which
> makes
> it really difficult for me to queue it up for -stable properly and
> reliably.
>
> Can you please repost this series? Hopefully it will work.
>
> If it doesn't work we'll ask the patchwork folks to take a look.
>
> Thanks!
Sure, I have rebased and resent.
Thanks.
prev parent reply other threads:[~2017-12-03 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 23:08 [PATCH net 0/2] tcp: fix SELinux/Smack corruptions Eric Dumazet
2017-12-01 23:08 ` [PATCH net 1/2] tcp: add tcp_v4_fill_cb()/tcp_v4_restore_cb() Eric Dumazet
2017-12-01 23:08 ` [PATCH net 2/2] tcp: use IPCB instead of TCP_SKB_CB in inet_exact_dif_match() Eric Dumazet
2017-12-03 15:42 ` [PATCH net 0/2] tcp: fix SELinux/Smack corruptions David Miller
2017-12-03 17:33 ` Eric Dumazet [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=1512322408.19682.55.camel@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=edumazet@google.com \
--cc=james.l.morris@oracle.com \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.