From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: jack@suse.cz, stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, "Daniel Díaz" <daniel.diaz@linaro.org>,
"Tom Rix" <trix@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: [PATCH 6.1 000/600] 6.1.53-rc1 review
Date: Tue, 12 Sep 2023 11:03:50 +0200 [thread overview]
Message-ID: <2023091217-reflux-playroom-017a@gregkh> (raw)
In-Reply-To: <CA+G9fYsiWEKSV0EeU0cXsJZ3U75fbdGyCmDx07ksFMUW5jouyw@mail.gmail.com>
On Tue, Sep 12, 2023 at 02:19:34PM +0530, Naresh Kamboju wrote:
> On Tue, 12 Sept 2023 at 07:55, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> >
> > Hello!
> >
> > On Mon, 11 Sept 2023 at 14:58, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> > > On 11/09/23 7:40 a. m., Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.53 release.
> > > > There are 600 patches in this series, all will be posted as a response
> > > > to this one. If anyone has any issues with these being applied, please
> > > > let me know.
> > > >
> > > > Responses should be made by Wed, 13 Sep 2023 13:44:56 +0000.
> > > > Anything received after that time might be too late.
> > > >
> > > > The whole patch series can be found in one patch at:
> > > > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.53-rc1.gz
> > > > or in the git tree and branch at:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > > We're seeing this new warning:
> > > -----8<-----
> > > /builds/linux/fs/udf/inode.c:892:6: warning: variable 'newblock' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized]
> > > 892 | if (*err < 0)
> > > | ^~~~~~~~
> > > /builds/linux/fs/udf/inode.c:914:9: note: uninitialized use occurs here
> > > 914 | return newblock;
> > > | ^~~~~~~~
> > > /builds/linux/fs/udf/inode.c:892:2: note: remove the 'if' if its condition is always false
> > > 892 | if (*err < 0)
> > > | ^~~~~~~~~~~~~
> > > 893 | goto out_free;
> > > | ~~~~~~~~~~~~~
> > > /builds/linux/fs/udf/inode.c:699:34: note: initialize the variable 'newblock' to silence this warning
> > > 699 | udf_pblk_t newblocknum, newblock;
> > > | ^
> > > | = 0
> > > 1 warning generated.
> > > ----->8-----
> > >
> > > That's with Clang 17 (and nightly) on:
> > > * arm
> > > * powerpc
> > > * s390
> >
> > For what it's worth, bisection points to 903b487b5ba6 ("udf: Handle
> > error when adding extent to a file").
>
> I see the following commit is fixing the reported problem.
>
> commit 6d5ab7c2f7cf90877dab8f2bb06eb5ca8edc73ef
> Author: Tom Rix <trix@redhat.com>
> Date: Fri Dec 30 12:53:41 2022 -0500
>
> udf: initialize newblock to 0
>
> The clang build reports this error
> fs/udf/inode.c:805:6: error: variable 'newblock' is used
> uninitialized whenever 'if' condition is true
> [-Werror,-Wsometimes-uninitialized]
> if (*err < 0)
> ^~~~~~~~
> newblock is never set before error handling jump.
> Initialize newblock to 0 and remove redundant settings.
>
> Fixes: d8b39db5fab8 ("udf: Handle error when adding extent to a file")
Ah, the Fixes: tag lied! There is no such git id in Linus's tree
anywhere, so our scripts couldn't match this up at all.
I'll go queue this fix up, thanks for digging it out.
greg k-h
next prev parent reply other threads:[~2023-09-12 9:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 13:40 [PATCH 6.1 000/600] 6.1.53-rc1 review Greg Kroah-Hartman
2023-09-11 13:42 ` [PATCH 6.1 102/600] eventfd: prevent underflow for eventfd semaphores Greg Kroah-Hartman
2023-09-11 20:13 ` [PATCH 6.1 000/600] 6.1.53-rc1 review Shuah Khan
2023-09-11 20:58 ` Daniel Díaz
2023-09-12 2:25 ` Daniel Díaz
2023-09-12 8:49 ` Naresh Kamboju
2023-09-12 9:03 ` Greg Kroah-Hartman [this message]
2023-09-12 10:32 ` Greg Kroah-Hartman
2023-09-12 11:56 ` Naresh Kamboju
2023-09-12 12:01 ` Greg Kroah-Hartman
2023-09-13 13:55 ` Naresh Kamboju
2023-09-12 5:50 ` Bagas Sanjaya
2023-09-12 9:00 ` Sudip Mukherjee (Codethink)
2023-09-12 9:03 ` Naresh Kamboju
2023-09-12 10:27 ` Takeshi Ogasawara
2023-09-12 12:37 ` Conor Dooley
2023-09-12 15:10 ` Jon Hunter
2023-09-12 17:35 ` Florian Fainelli
2023-09-12 18:35 ` Guenter Roeck
2023-09-13 2:40 ` Ron Economos
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=2023091217-reflux-playroom-017a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=daniel.diaz@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=jack@suse.cz \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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