From: "Mateusz Stępień" <mateusz.stepien@netrounds.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Old content of /proc/net after switching network namespace
Date: Mon, 7 Jan 2019 09:54:26 +0100 [thread overview]
Message-ID: <165a35df-0a38-3507-fb8d-0f4b45af0dc3@netrounds.com> (raw)
In-Reply-To: <20190104110933.GA2682@avx2>
Thank you for the quick response, unfortunately the patch does not work,
problem still persist.
I saw the other mail thread, and it looks like the proper solution
described by Al will take some time. I don't know if we can afford right
now to write a proper patch ourselves, also at least my understanding is
that this is a regression, so my question is: can we expect a proper
patch in a coming weeks? If not, will reverting the patch at fault have
any more negative side effects? Of course it will bring back the
behaviour it was supposed to fix, but are there any other issues?
Thanks,
Mateusz
next prev parent reply other threads:[~2019-01-07 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 8:21 Mateusz Stępień
2019-01-04 11:09 ` Alexey Dobriyan
2019-01-07 8:54 ` Mateusz Stępień [this message]
2019-01-07 12:39 ` Alexey Dobriyan
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=165a35df-0a38-3507-fb8d-0f4b45af0dc3@netrounds.com \
--to=mateusz.stepien@netrounds.com \
--cc=adobriyan@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®