From: Conor Dooley <conor@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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
Subject: Re: [PATCH 6.0 0000/1066] 6.0.16-rc2 review
Date: Sat, 31 Dec 2022 00:09:13 +0000 [thread overview]
Message-ID: <Y699qYnUYUwFuQ/E@spud> (raw)
In-Reply-To: <20221230094059.698032393@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
Hey Greg,
On Fri, Dec 30, 2022 at 10:49:23AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.0.16 release.
> There are 1066 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 Sun, 01 Jan 2023 09:38:41 +0000.
> Anything received after that time might be too late.
> Paulo Alcantara <pc@cjr.nz>
> cifs: improve symlink handling for smb2+
This patch here appears to fail allmodconfig + LLVM on RISC-V:
../fs/cifs/smb2inode.c:419:4: error: variable 'idata' is uninitialized when used here [-Werror,-Wuninitialized]
idata->symlink_target = kstrdup(cfile->symlink_target, GFP_KERNEL);
^~~~~
../fs/cifs/smb2inode.c:76:35: note: initialize the variable 'idata' to silence this warning
struct cifs_open_info_data *idata;
^
= NULL
1 error generated.
It looks like this was reported as a smatch error on Christmas Day:
https://lore.kernel.org/all/202212250020.fyWQFNzF-lkp@intel.com/
Given the day in question, missing that report seems pretty
understandable :)
I tried to see if this had been reported already against the patches
themselves, rather than Sasha's queue, but given the size of the patchset
I may have missed it. Apologies for the noise if I have.
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-12-31 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 9:49 [PATCH 6.0 0000/1066] 6.0.16-rc2 review Greg Kroah-Hartman
2022-12-30 17:07 ` Slade Watkins
2022-12-30 17:47 ` Florian Fainelli
2022-12-30 20:58 ` Allen Pais
2022-12-31 0:09 ` Conor Dooley [this message]
2022-12-31 5:52 ` Guenter Roeck
2022-12-31 11:48 ` Greg Kroah-Hartman
2022-12-31 0:17 ` Guenter Roeck
2022-12-31 0:18 ` Guenter Roeck
2022-12-31 3:47 ` Bagas Sanjaya
2022-12-31 9:12 ` Naresh Kamboju
2022-12-31 11:01 ` Ron Economos
-- strict thread matches above, loose matches on Subject: below --
2022-12-30 19:23 Joel Fernandes
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=Y699qYnUYUwFuQ/E@spud \
--to=conor@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.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 \
/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