From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>,
"Zachary M. Raines" <zachary.raines@canonical.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
JP Kobryn <jp.kobryn@linux.dev>
Subject: Re: PROBLEM: Duplicated entries in /proc/<pid>/mountinfo
Date: Wed, 25 Feb 2026 11:55:07 -0500 [thread overview]
Message-ID: <5a1f3e553f47a34b1cd6c30d9ec3649919d46585.camel@kernel.org> (raw)
In-Reply-To: <20260214-filmt-seepferdchen-c917d60205dc@brauner>
On Sat, 2026-02-14 at 13:28 +0100, Christian Brauner wrote:
> On Wed, Feb 11, 2026 at 12:59:25PM -0600, Zachary M. Raines wrote:
> > On Thu Jan 29, 2026 at 1:04 PM CST, Zachary M. Raines wrote:
> > > On Thu Jan 29, 2026 at 8:28 AM CST, Christian Brauner wrote:
> > > > On Wed, Jan 28, 2026 at 08:49:12AM -0600, Zachary M. Raines wrote:
> > > > I suspect the issue is real though. I'm appending a patch as a proposed
> > > > fix. Can you test that and report back, please? I'm traveling tomorrow
> > > > so might take a little.
> >
> > Just following up on the patch you sent and thanks again.
> >
> > > Thank you for the quick turnaround on that patch. I applied it on top
> > > of 6.19-rc7 and after about 3 hrs I haven't seen any duplicates, in
> > > contrast to without the patch where they appear in under 10 minutes.
> > >
> > > Let me know if there's any other testing that would help.
> >
> > According to my testing, your patch resolves the issue. Do you plan to
> > submit it upstream? Please let me know if there's anything
> > I can do to help on that front.
>
> It'll go upstream early next week. :) I deferred some pull requests.
I noticed that this still hasn't gone to Linus and it's marked for
stable in your tree. Any reason you're waiting on it?
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-02-25 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 14:49 Zachary M. Raines
2026-01-29 14:28 ` Christian Brauner
2026-01-29 19:04 ` Zachary M. Raines
2026-02-11 18:59 ` Zachary M. Raines
2026-02-14 12:28 ` Christian Brauner
2026-02-25 16:55 ` Jeff Layton [this message]
2026-02-26 8:20 ` Christian Brauner
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=5a1f3e553f47a34b1cd6c30d9ec3649919d46585.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=brauner@kernel.org \
--cc=jp.kobryn@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zachary.raines@canonical.com \
/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®