netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mikevs@xs4all.net
Cc: git.user@gmail.com, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: net: prevent of emerging cross-namespace symlinks patches for 3.14?
Date: Mon, 19 Jan 2015 21:19:30 -0500 (EST)	[thread overview]
Message-ID: <20150119.211930.968922094604288712.davem@davemloft.net> (raw)
In-Reply-To: <54BC3EF2.5080403@xs4all.net>

From: Miquel van Smoorenburg <mikevs@xs4all.net>
Date: Mon, 19 Jan 2015 00:17:06 +0100

> On 15/01/15 19:39, Alexander Y. Fomichev wrote:
>> On Thu, Jan 15, 2015 at 12:45 AM, Miquel van Smoorenburg
>> mikevs@xs4all.net> wrote:
>>> [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.704892] sysfs: cannot create
>>> duplicate
>>> filename '/devices/virtual/net/eth0.104/upper_eth0'
>>> I did not see these errors in 3.12. This was fixed in 3.17
>>
>> Hi,
>>
>> no objections of course,
>> actually it was written and tested with 3.14 in mind.
> 
> David, could you have a quick look and ack this if you agree this
> should go in 3.14-stable ?

Yes, this is fine, thanks for asking.

  reply	other threads:[~2015-01-20  2:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 21:45 net: prevent of emerging cross-namespace symlinks patches for 3.14? Miquel van Smoorenburg
2015-01-15 18:39 ` Alexander Y. Fomichev
2015-01-18 23:17   ` Miquel van Smoorenburg
2015-01-20  2:19     ` David Miller [this message]
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=20150119.211930.968922094604288712.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=git.user@gmail.com \
    --cc=mikevs@xs4all.net \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).