From: Michal Kubecek <mkubecek@suse.cz>
To: David Miller <davem@davemloft.net>
Cc: cernekee@chromium.org, johannes.berg@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
daniel@iogearbox.net, dsahern@gmail.com
Subject: Re: [PATCH V2] netlink: Add netns check on taps
Date: Mon, 11 Dec 2017 17:13:50 +0100 [thread overview]
Message-ID: <20171211161350.s5ki6peee2oxpric@unicorn.suse.cz> (raw)
In-Reply-To: <20171206.155714.908446002721815545.davem@davemloft.net>
On Wed, Dec 06, 2017 at 03:57:14PM -0500, David Miller wrote:
> From: Kevin Cernekee <cernekee@chromium.org>
> Date: Wed, 6 Dec 2017 12:12:27 -0800
>
> > Currently, a nlmon link inside a child namespace can observe systemwide
> > netlink activity. Filter the traffic so that nlmon can only sniff
> > netlink messages from its own netns.
> >
> > Test case:
> >
> > vpnns -- bash -c "ip link add nlmon0 type nlmon; \
> > ip link set nlmon0 up; \
> > tcpdump -i nlmon0 -q -w /tmp/nlmon.pcap -U" &
> > sudo ip xfrm state add src 10.1.1.1 dst 10.1.1.2 proto esp \
> > spi 0x1 mode transport \
> > auth sha1 0x6162633132330000000000000000000000000000 \
> > enc aes 0x00000000000000000000000000000000
> > grep --binary abc123 /tmp/nlmon.pcap
> >
> > Signed-off-by: Kevin Cernekee <cernekee@chromium.org>
>
> Applied and queued up for -stable, thanks Kevin.
David,
this patch is marked as accepted in patchworks and listed in
http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
but it's not in the net tree. Is there a problem with it?
Michal Kubecek
next prev parent reply other threads:[~2017-12-11 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 20:12 [PATCH V2] netlink: Add netns check on taps Kevin Cernekee
2017-12-06 20:57 ` David Miller
2017-12-11 16:13 ` Michal Kubecek [this message]
2017-12-11 16:58 ` David Miller
2017-12-11 17:22 ` Michal Kubecek
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=20171211161350.s5ki6peee2oxpric@unicorn.suse.cz \
--to=mkubecek@suse.cz \
--cc=cernekee@chromium.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox