From: Eric Dumazet <eric.dumazet@gmail.com>
To: Guillaume Nault <g.nault@alphalink.fr>,
Tom Herbert <tom@herbertland.com>
Cc: netdev@vger.kernel.org, James Chapman <jchapman@katalix.com>
Subject: Re: [PATCH net-next] kcm: do not attach sockets if sk_user_data is already used
Date: Tue, 16 Jan 2018 09:10:59 -0800 [thread overview]
Message-ID: <1516122659.3606.9.camel@gmail.com> (raw)
In-Reply-To: <20180116104425.GA1394@alphalink.fr>
On Tue, 2018-01-16 at 11:44 +0100, Guillaume Nault wrote:
>
> Tom, if I understand KCM correctly, it only makes sense to attach it to
> SOCK_STREAM sockets. Shouldn't that be enforced? Maybe we should
> restrict it even further, so that only known KCM-safe sockets could be
> attached (that is, reject anything that isn't AF_INET* | SOCK_STREAM).
I believe I asked the same question months ago. I had no answer.
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/comm
it/?id=351050ecd6523374b370341cc29fe61e2201556b
Not sure if anyone uses KCM, other than fuzzers ?
next prev parent reply other threads:[~2018-01-16 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 11:32 [PATCH net-next] kcm: do not attach sockets if sk_user_data is already used James Chapman
2018-01-16 10:44 ` Guillaume Nault
2018-01-16 17:10 ` Eric Dumazet [this message]
2018-01-16 17:36 ` Tom Herbert
2018-01-16 19:00 ` David Miller
2018-01-17 11:13 ` James Chapman
2018-01-17 19:25 ` David Miller
2018-01-18 15:18 ` Guillaume Nault
2018-01-18 15:40 ` James Chapman
2018-01-18 16:29 ` Guillaume Nault
2018-01-18 17:30 ` James Chapman
2018-01-18 17:46 ` Tom Herbert
2018-01-18 18:08 ` Eric Dumazet
2018-01-18 19:26 ` Tom Herbert
2018-01-18 19:46 ` Eric Dumazet
2018-01-18 17:40 ` Tom Herbert
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=1516122659.3606.9.camel@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=g.nault@alphalink.fr \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
--cc=tom@herbertland.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 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.