From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jan Kara" <jack@suse.cz>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Jan Kara" <jack@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] quota: avoid printing an uninitialized blk number
Date: Tue, 13 Feb 2024 11:26:57 +0100 [thread overview]
Message-ID: <3c76ba23-e4d7-49b0-b53c-b60772a25891@app.fastmail.com> (raw)
In-Reply-To: <20240213102139.gnfh5sq24rwu7wnp@quack3>
On Tue, Feb 13, 2024, at 11:21, Jan Kara wrote:
> On Tue 13-02-24 11:17:28, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> The error path of find_tree_dqentry() now prints a variable that is
>> never initialized:
>>
>> fs/quota/quota_tree.c:674:8: error: variable 'blk' is uninitialized when used here [-Werror,-Wuninitialized]
>> blk);
>> ^~~
>> include/linux/quotaops.h:34:41: note: expanded from macro 'quota_error'
>> __quota_error((sb), __func__, fmt , ## args)
>> ^~~~
>>
>> Move the calculation of the block number slightly up to make it
>> show a sensible number.
>>
>> Fixes: 223bfb57631b ("quota: Detect loops in quota tree")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Arnd, this should be fixed in my tree as of yesterday and I can see that
> you've even based your patch on a fixed kernel :)
Right, sorry about that. I did a lot of fixes yesterday and
sent them out after making sure they did not cause any new
failures in an overnight test build, but did not check carefully
during rebasing.
Arnd
prev parent reply other threads:[~2024-02-13 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 10:17 [PATCH] quota: avoid printing an uninitialized blk number Arnd Bergmann
2024-02-13 10:21 ` Jan Kara
2024-02-13 10:26 ` Arnd Bergmann [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=3c76ba23-e4d7-49b0-b53c-b60772a25891@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.