From: Markus Elfring <Markus.Elfring@web.de>
To: Steve French <smfrench@gmail.com>,
linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
Bharath SM <bharathsm@microsoft.com>,
Paulo Alcantara <pc@manguebit.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Steve French <sfrench@samba.org>, Tom Talpey <tom@talpey.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] smb: client: Simplify a return statement in get_smb2_acl_by_path()
Date: Thu, 9 Oct 2025 17:44:54 +0200 [thread overview]
Message-ID: <ccb38a9b-4192-4863-9b29-497b55d99a6a@web.de> (raw)
In-Reply-To: <CAH2r5mvg=kqPyA2nYF=Nhjr3vkt4dT1R4p-Bk_MBQtddjx_EhA@mail.gmail.com>
> As pointed out by the kernel test robot a few minutes ago, this patch
> would introduce a regression (uninitialized rc variable in free_xid
> macro), so will remove this patch from for-next.
Will this (clang) compiler report be reconsidered once more under other circumstances?
…>> +++ b/fs/smb/client/smb2ops.c
>> @@ -3216,9 +3216,8 @@ get_smb2_acl_by_path(struct cifs_sb_info *cifs_sb,
>>
>> utf16_path = cifs_convert_path_to_utf16(path, cifs_sb);
>> if (!utf16_path) {
>> - rc = -ENOMEM;
>> free_xid(xid);
>> - return ERR_PTR(rc);
>> + return ERR_PTR(-ENOMEM);
>> }
>>
>> oparms = (struct cifs_open_parms) {
…
Can it be that the uninitialized rc variable would not really matter for
the adjusted statements in such an if branch?
Regards,
Markus
next prev parent reply other threads:[~2025-10-09 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 20:02 [PATCH] smb: client: Simplify a return statement in get_smb2_acl_by_path() Markus Elfring
2025-10-09 0:12 ` Steve French
[not found] ` <CAH2r5mtpoLscs9sodXcRMO3-dqMDBSTR+ncExdqy4dQR=4uE8A@mail.gmail.com>
2025-10-09 5:17 ` Markus Elfring
[not found] ` <CAH2r5mtY8--9ccnm5aYfOYJ=kEBr7=y-Z_eROKDp7A6DGnxwcA@mail.gmail.com>
2025-10-09 14:00 ` Markus Elfring
2025-10-09 14:10 ` Steve French
2025-10-09 15:29 ` [PATCH] " Steve French
2025-10-09 15:44 ` Markus Elfring [this message]
2025-10-10 7:22 ` Markus Elfring
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=ccb38a9b-4192-4863-9b29-497b55d99a6a@web.de \
--to=markus.elfring@web.de \
--cc=bharathsm@microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.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