From: Eric Van Hensbergen <ericvh@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: v9fs@lists.linux.dev
Subject: Re: [bug report] fs/9p: mitigate inode collisions
Date: Wed, 17 Apr 2024 13:50:34 -0500 [thread overview]
Message-ID: <CAFkjPTkWEV6aBAzgcgOB_fX_6C7notJB55y-m0tkQOHCnPMe9A@mail.gmail.com> (raw)
In-Reply-To: <5d527d1e-95de-4e36-845a-897cabdcaccd@moroto.mountain>
On Wed, Apr 17, 2024 at 1:12 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
>
> Hello Eric Van Hensbergen,
>
> Commit 6ae7784008d9 (" fs/9p: mitigate inode collisions") from Apr
> 15, 2024 (linux-next), leads to the following Smatch static checker
> warning:
>
> fs/9p/vfs_inode.c:513 v9fs_remove()
> error: uninitialized symbol 'v9fid'.
>
Thanks for this, I've amended the patch to remove the print in
question since it was actually vestigial telemetry while I was
debugging and shouldn't have been in the patch in the first place.
-eric
prev parent reply other threads:[~2024-04-17 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:11 [bug report] fs/9p: mitigate inode collisions Dan Carpenter
2024-04-17 18:50 ` Eric Van Hensbergen [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=CAFkjPTkWEV6aBAzgcgOB_fX_6C7notJB55y-m0tkQOHCnPMe9A@mail.gmail.com \
--to=ericvh@kernel.org \
--cc=dan.carpenter@linaro.org \
--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).