From: Daniel Borkmann <dborkman@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: luto@amacapital.net, torvalds@linux-foundation.org,
kaber@trash.net, netdev@vger.kernel.org, tgraf@suug.ch
Subject: Re: Netlink mmap tx security?
Date: Thu, 16 Oct 2014 01:45:22 +0200 [thread overview]
Message-ID: <543F0712.8080503@redhat.com> (raw)
In-Reply-To: <20141014.220111.179628329028952302.davem@davemloft.net>
On 10/15/2014 04:01 AM, David Miller wrote:
> From: Andy Lutomirski <luto@amacapital.net>
> Date: Tue, 14 Oct 2014 15:16:46 -0700
>
>> It's at least remotely possible that there's something that assumes
>> that assumes that the availability of NETLINK_RX_RING implies
>> NETLINK_TX_RING, which would be unfortunate.
>
> I already found one such case, nlmon :-/
Hmm, can you elaborate? I currently don't think that nlmon cares
actually.
next prev parent reply other threads:[~2014-10-15 23:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALCETrWsCqy7KEKPTOeHjrO1c2JE1E_seO_J+yA=sYFhS11NXQ@mail.gmail.com>
2014-05-12 21:08 ` Netlink mmap tx security? Andy Lutomirski
2014-10-11 22:29 ` Andy Lutomirski
2014-10-11 23:09 ` David Miller
2014-10-14 19:19 ` David Miller
2014-10-14 19:33 ` Andy Lutomirski
2014-10-14 20:00 ` David Miller
2014-10-14 22:16 ` Andy Lutomirski
2014-10-15 2:01 ` David Miller
2014-10-15 2:03 ` Andy Lutomirski
2014-10-15 2:09 ` David Miller
2014-10-16 6:45 ` Daniel Borkmann
2014-10-16 7:07 ` Thomas Graf
2014-12-16 22:58 ` David Miller
2014-12-16 23:58 ` Daniel Borkmann
2014-12-17 16:27 ` Thomas Graf
2014-12-18 17:36 ` David Miller
2014-12-17 0:02 ` Eric Dumazet
2014-12-17 16:26 ` Thomas Graf
2014-12-18 10:30 ` [PATCH net] netlink: Don't reorder loads/stores before marking mmap netlink frame as available Thomas Graf
2014-12-18 17:36 ` David Miller
2014-12-18 19:13 ` Linus Torvalds
2014-10-15 23:45 ` Daniel Borkmann [this message]
2014-10-15 23:57 ` Netlink mmap tx security? David Miller
2014-10-15 23:58 ` Andy Lutomirski
2014-10-16 3:34 ` David Miller
2014-10-16 5:52 ` Thomas Graf
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=543F0712.8080503@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=torvalds@linux-foundation.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.