From: Greg KH <greg@kroah.com>
To: Arne Welzel <arne.welzel@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Opening /proc/<pid>/net/dev prevents network namespace from expiring
Date: Mon, 24 Aug 2020 09:42:23 +0200 [thread overview]
Message-ID: <20200824074223.GA4133866@kroah.com> (raw)
In-Reply-To: <CAEyJRx0Zd_jtH1JQCSYYrdc-YTa8yvtneaurUKXEKK32-kWfRA@mail.gmail.com>
On Sat, Aug 22, 2020 at 11:05:53PM +0200, Arne Welzel wrote:
> Hello,
>
> as an unprivileged user one is able to keep network namespaces from
> expiring by opening /proc/<pid>/net/dev of other processes. I've previously
> put this on stackexchange [1] and then bugzilla [2]. That's been a while
> though, so posting here for a bit more visibility in case it's something
> that's worth fixing.
The proper place to send networking bugs/issues is to the networking
developers themselves, at netdev@vger.kernel.org.
Try sending it there, no kernel developers use stackexchange for
development :)
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-08-24 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-22 21:05 Opening /proc/<pid>/net/dev prevents network namespace from expiring Arne Welzel
2020-08-24 7:42 ` Greg KH [this message]
2020-08-24 16:53 ` Grant Taylor
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=20200824074223.GA4133866@kroah.com \
--to=greg@kroah.com \
--cc=arne.welzel@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).