From: Miquel van Smoorenburg <mikevs@xs4all•net>
To: netdev@vger•kernel.org
Cc: stable@vger•kernel.org,
"Alexander Y. Fomichev" <git.user@gmail•com>,
David Miller <davem@davemloft•net>
Subject: net: prevent of emerging cross-namespace symlinks patches for 3.14?
Date: Wed, 14 Jan 2015 22:45:19 +0100 [thread overview]
Message-ID: <54B6E36F.9060703@xs4all.net> (raw)
[first sent to lkml, now to netdev and the original patch author]
When running 'lxc' on the latest -stable kernel, 3.14.28, I'm seeing
these errors:
Jan 14 17:47:16 lxc2 kernel: [ 10.704890] WARNING: CPU: 0 PID: 3209 at
fs/sys
fs/dir.c:52 sysfs_warn_dup+0x8c/0xb0()
Jan 14 17:47:16 lxc2 kernel: [ 10.704892] sysfs: cannot create
duplicate filename '/devices/virtual/net/eth0.104/upper_eth0'
Jan 14 17:47:16 lxc2 kernel: [ 10.704954] CPU: 0 PID: 3209 Comm:
lxc-autostart Not tainted 3.14.28-xsserver #1
I did not see these errors in 3.12. This was fixed in 3.17 by:
net: prevent of emerging cross-namespace symlinks
https://github.com/torvalds/linux/commit/4c75431ac3520631f1d9e74aa88407e6374dbbc4
net: fix creation adjacent device symlinks
https://github.com/torvalds/linux/commit/7ce64c79c4decdeb1afe0bf2f6ef834b382871d1
These patches apply cleanly to 3.14.28.
If you agree that this should go into 3.14-stable, please ack.
Thanks,
Mike.
next reply other threads:[~2015-01-14 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 21:45 Miquel van Smoorenburg [this message]
2015-01-15 18:39 ` net: prevent of emerging cross-namespace symlinks patches for 3.14? Alexander Y. Fomichev
2015-01-18 23:17 ` Miquel van Smoorenburg
2015-01-20 2:19 ` David Miller
2015-01-23 12:14 ` Luis Henriques
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=54B6E36F.9060703@xs4all.net \
--to=mikevs@xs4all$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=git.user@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stable@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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