From: Dominique Martinet <asmadeus@codewreck.org>
To: Al Viro <viro@zeniv.linux.org.uk>,
Chandan Babu R <chandanbabu@kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs@vger.kernel.org, brauner@kernel.org, jack@suse.cz
Subject: Re: [BUG REPORT] shrink_dcache_parent() loops indefinitely on a next-20240102 kernel
Date: Sat, 3 Feb 2024 22:05:28 +0900 [thread overview]
Message-ID: <Zb46GLPxQNnx16fe@codewreck.org> (raw)
In-Reply-To: <8734ulsykv.fsf@debian-BULLSEYE-live-builder-AMD64>
Hello -- I've also hit this on master as of a few days ago (on
021533194476 ("Kconfig: Disable -Wstringop-overflow for GCC globally"))
just running some short lived docker container in a loop -- the last
process of the mount namespace exiting cleans up the mess docker had set
up and sometimes get caught there:
#5 [ffff9f0fcd927c48] select_collect at ffffffffb2ffa6c2
#6 [ffff9f0fcd927c58] d_walk at ffffffffb2ffb0a8
#7 [ffff9f0fcd927cb0] shrink_dcache_parent at ffffffffb2ffd53e
#8 [ffff9f0fcd927cf8] shrink_dcache_for_umount at ffffffffb2ffd8e7
#9 [ffff9f0fcd927d20] generic_shutdown_super at ffffffffb2fdc39a
#10 [ffff9f0fcd927d38] kill_litter_super at ffffffffb2fdc673
#11 [ffff9f0fcd927d50] deactivate_locked_super at ffffffffb2fdd37f
#12 [ffff9f0fcd927d68] cleanup_mnt at ffffffffb3008d1d
#13 [ffff9f0fcd927d90] task_work_run at ffffffffb2cd97e9
#14 [ffff9f0fcd927db0] do_exit at ffffffffb2cb1c9c
#15 [ffff9f0fcd927e10] do_group_exit at ffffffffb2cb264d
#16 [ffff9f0fcd927e38] __x64_sys_exit_group at ffffffffb2cb26c4
#17 [ffff9f0fcd927e40] do_syscall_64 at ffffffffb376ea47
(I'm trying to reproduce another networking bug with that, it doesn't
happen very often but I noticed docker hangs once in a while, more often
after I reduced how much memory I gave to this VM)
Reverting just 57851607326a ("get rid of DCACHE_GENOCIDE") seems to get
rid of the issue at this point, I'm pretty confident it's no longer
happening by now but I'll reply again tomorrow if I hit the problem
again overnight.
Thanks,
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2024-02-03 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 6:42 [BUG REPORT] shrink_dcache_parent() loops indefinitely on a next-20240102 kernel Chandan Babu R
2024-01-04 4:34 ` Darrick J. Wong
2024-01-04 13:10 ` Chandan Babu R
2024-01-18 5:29 ` Chandan Babu R
2024-01-18 6:39 ` Al Viro
2024-01-23 6:01 ` Chandan Babu R
2024-01-23 11:40 ` Al Viro
2024-01-25 6:31 ` Chandan Babu R
2024-02-03 13:05 ` Dominique Martinet [this message]
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=Zb46GLPxQNnx16fe@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=brauner@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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