From: Nick Desaulniers <ndesaulniers@google.com>
To: Tom Rix <trix@redhat.com>
Cc: jack@suse.com, nathan@kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] udf: remove reporting loc in debug output
Date: Wed, 1 Feb 2023 15:14:33 -0800 [thread overview]
Message-ID: <Y9ryWROdCrKYWBzY@google.com> (raw)
In-Reply-To: <20230127162906.872395-1-trix@redhat.com>
On Fri, Jan 27, 2023 at 08:29:06AM -0800, Tom Rix wrote:
> clang build fails with
> fs/udf/partition.c:86:28: error: variable 'loc' is uninitialized when used here [-Werror,-Wuninitialized]
> sb, block, partition, loc, index);
> ^~~
>
> loc is now only know when bh is valid. So remove reporting loc in debug output.
typo: s/know/known/
>
> Fixes: 4215db46d538 ("udf: Use udf_bread() in udf_get_pblock_virt15()")
> Signed-off-by: Tom Rix <trix@redhat.com>
Thanks Tom, kernelci has also been reporting this.
https://lore.kernel.org/linux-next/?q=error%3A+variable+%27loc%27+is+uninitialized+when+used+here
Reported-by: "kernelci.org bot" <bot@kernelci.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
> ---
> fs/udf/partition.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/udf/partition.c b/fs/udf/partition.c
> index 92765d2f6958..5bcfe78d5cab 100644
> --- a/fs/udf/partition.c
> +++ b/fs/udf/partition.c
> @@ -82,8 +82,8 @@ uint32_t udf_get_pblock_virt15(struct super_block *sb, uint32_t block,
>
> bh = udf_bread(sbi->s_vat_inode, newblock, 0, &err);
> if (!bh) {
> - udf_debug("get_pblock(UDF_VIRTUAL_MAP:%p,%u,%u) VAT: %u[%u]\n",
> - sb, block, partition, loc, index);
> + udf_debug("get_pblock(UDF_VIRTUAL_MAP:%p,%u,%u)\n",
> + sb, block, partition);
> return 0xFFFFFFFF;
> }
>
> --
> 2.26.3
>
>
next prev parent reply other threads:[~2023-02-01 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 16:29 [PATCH] udf: remove reporting loc in debug output Tom Rix
2023-01-27 17:53 ` Nathan Chancellor
2023-02-01 23:14 ` Nick Desaulniers [this message]
2023-02-07 11:01 ` Jan Kara
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=Y9ryWROdCrKYWBzY@google.com \
--to=ndesaulniers@google.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=trix@redhat.com \
/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