Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: ditang chen <ditang.c@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk, ebiederm@xmission.com
Subject: Re: fs/pnode.c: propagate_one Oops in ltp/fs_bind test
Date: Tue, 29 Nov 2022 11:25:24 +0100	[thread overview]
Message-ID: <20221129102524.ulsthvmf6tbfwhmb@wittgenstein> (raw)
In-Reply-To: <CAHnGgyHAo+XQPchU4HaKshFbnyHYuD0EuHy17QvPRAZ4MFVq-w@mail.gmail.com>

On Tue, Nov 15, 2022 at 11:04:01PM +0800, ditang chen wrote:
> Here is a reproducer:
> 1. Run netns.sh script in loop
> # while true; do ./netns.sh; done
> # cat netns.sh
> #!/bin/bash
> num=1000
> function create_netns()
> {
> for((i=0; i<$num; i++))
> do
>   ip netns add local$i
>   ip netns exec local$i pwd &
> done
> }
> function clean_netns()
> {
> for((i=0; i<$num; i++))
> do
>     ip netns del local$i
> done
> }
> create_netns
> clean_netns
> 
> 2.  run fs_bind/fs_bind24 in loop, fs_bind24 only
> # cat /opt/ltp/runtest/fs_bind
> #DESCRIPTION:Bind mounts and shared subtrees
> fs_bind24_sh fs_bind24.sh
> # while true; do /opt/ltp/runltp -f fs_bind; done
> 
> This oops also exists in the latest kernel code:

I've been running this since yesterday on v6.1-rc7 to reproduce and it
didn't trigger. It's unclear whether you're saying that you've managed
to reproduce this on mainline. It doesn't seem to be.

  reply	other threads:[~2022-11-29 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 15:04 fs/pnode.c: propagate_one Oops in ltp/fs_bind test ditang chen
2022-11-29 10:25 ` Christian Brauner [this message]
     [not found]   ` <CAHnGgyEQjcGSDPC=k-ikGQC460jov2bum0AzjD+Jm-8fDwXGbg@mail.gmail.com>
2022-12-05 14:34     ` ditang chen

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=20221129102524.ulsthvmf6tbfwhmb@wittgenstein \
    --to=brauner@kernel.org \
    --cc=ditang.c@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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