From: "asmadeus@codewreck.org" <asmadeus@codewreck.org>
To: Albert Guo <aguo@vmware.com>
Cc: v9fs@lists.linux.dev
Subject: Re: [syzbot] WARNING: refcount bug in p9_client_walk
Date: Wed, 15 Nov 2023 16:06:43 +0900 [thread overview]
Message-ID: <ZVRuAzFQfLX162ye@codewreck.org> (raw)
In-Reply-To: <PH0PR05MB832071E5E0944D7C5CEA81DFB3B1A@PH0PR05MB8320.namprd05.prod.outlook.com>
Albert Guo wrote on Wed, Nov 15, 2023 at 03:50:48AM +0000:
> Hi Asemadeus,
Please always cc the subsystem's mailing list when asking such
questions; there's no point in singling out maintainers.
(And it'd really help if you wouldn't mispell names; although I guess
you could also say it does help since rilled up folks are more likely to
answer...)
> I’m Albert Guo from VMware. Sorry to disturb you. I’m writing to you to seek some help for Linux 9p driver.
> We use 9p driver in our product. We seem to encounter similar refcount issue in our test:
> [syzbot] WARNING: refcount bug in p9_client_walk
> https://groups.google.com/g/syzkaller-bugs/c/UrvjxOLiykQ/m/LlVAtCzQBQAJ?pli=1
>
> syzbot
> 2023年3月23日 06:02:37
>
> 收件人 syzkall...@googlegroups.com<mailto:syzkall...@googlegroups.com>
> Auto-closing this bug as obsolete.
> No recent activity, existing reproducers are no longer triggering the issue.
>
>
> Looks like the issue isn’t reproducible from syzbot? Is it fixed? Do
> you know which commit fix the issue?
It might have been fixed in 26273ade77f54716e30dfd40ac6e85ceb54ac0f9 as
uninitialized use could be causing that, otherwise I don't know --
there's been no other fix around refcounting since that report...
> Our kernel version is 6.1.56: https://elixir.bootlin.com/linux/v6.1.56/source
But it's long been fixed (included in 6.2 and 6.1.2), so there must be
another problem.
Please give your full stack trace (and not just a link to syzbot); the
warn message might help.
Also, how often do you hit this? (Can we consider it "reproductible"
under test where you would be able to run with tracepoints, or
simplifying the load etc?)
--
Dominique Martinet | Asmadeus
parent reply other threads:[~2023-11-15 7:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <PH0PR05MB832071E5E0944D7C5CEA81DFB3B1A@PH0PR05MB8320.namprd05.prod.outlook.com>]
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=ZVRuAzFQfLX162ye@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=aguo@vmware.com \
--cc=v9fs@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).