From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: marcelo.leitner@gmail.com, netdev@vger.kernel.org,
vyasevich@gmail.com, linux-sctp@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sctp: add new getsockopt option SCTP_SOCKOPT_PEELOFF_KERNEL
Date: Wed, 15 Jul 2015 13:58:24 -0700 (PDT) [thread overview]
Message-ID: <20150715.135824.754282841801954470.davem@davemloft.net> (raw)
In-Reply-To: <20150715131827.GA24091@hmsreliant.think-freely.org>
From: Neil Horman <nhorman@tuxdriver.com>
Date: Wed, 15 Jul 2015 09:18:28 -0400
> Do we need to do something here to prevent user space calls from inadvertently
> accessing this option?
And this is also not what I had anticipated was the implementation.
I didn't mean that adding a new option number specially for the
kernel was the right thing to do.
I meant that having a specific function GPL exported to modules that
the external code calls would do the trick.
That's why we have things like kernel_sendmsg() et al.
next prev parent reply other threads:[~2015-07-15 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 17:13 [PATCH v2 0/2] Avoid link dependency of dlm on sctp module Marcelo Ricardo Leitner
2015-07-14 17:13 ` [PATCH v2 1/2] sctp: add new getsockopt option SCTP_SOCKOPT_PEELOFF_KERNEL Marcelo Ricardo Leitner
2015-07-15 13:18 ` Neil Horman
2015-07-15 13:24 ` Marcelo Ricardo Leitner
2015-07-15 20:58 ` David Miller [this message]
2015-07-16 13:50 ` Vlad Yasevich
2015-07-16 14:03 ` Marcelo Ricardo Leitner
2015-07-20 18:53 ` Marcelo Ricardo Leitner
2015-07-22 13:13 ` David Laight
2015-07-22 13:50 ` Marcelo
2015-07-14 17:13 ` [PATCH v2 2/2] dlm: avoid using sctp_do_peeloff directly Marcelo Ricardo Leitner
2015-07-15 13:57 ` [PATCH v2 0/2] Avoid link dependency of dlm on sctp module Neil Horman
2015-07-15 20:59 ` David Miller
2015-07-16 11:18 ` Neil Horman
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=20150715.135824.754282841801954470.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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;
as well as URLs for NNTP newsgroup(s).