[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad8ef7da-db2a-4033-8701-cf2fc61b8a1d@samba.org>
Date: Mon, 24 Nov 2025 15:40:59 +0100
From: Stefan Metzmacher <metze@...ba.org>
To: David Howells <dhowells@...hat.com>
Cc: Steve French <sfrench@...ba.org>, Paulo Alcantara <pc@...guebit.org>,
Shyam Prasad N <sprasad@...rosoft.com>, linux-cifs@...r.kernel.org,
netfs@...ts.linux.dev, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, Tom Talpey <tom@...pey.com>
Subject: Re: [PATCH v4 07/11] cifs: Clean up some places where an extra kvec[]
was required for rfc1002
Am 24.11.25 um 15:36 schrieb David Howells:
> Hi Stefan,
>
> Stefan Metzmacher <metze@...ba.org> wrote:
>
>> I had to squash this into the patch
>>
>> I'm using smatch when building and got the following error
>> with this change:
>>
>> client/transport.c:1073 compound_send_recv() error: we previously assumed 'resp_iov' could be null (see line 1051)
>> ...
>> if ((ses->ses_status == SES_NEW) || (optype & CIFS_NEG_OP) || (optype & CIFS_SESS_OP)) {
>
> In this case smatch is wrong, though it can't work this out as the context
> spans more than one file. This clause applies only to certain operations
> (such as session setup and negotiate) that will always have a response buffer.
> But I've no objection to adding this warning to splat the warning.
Ok, I can just squash as well as the EIO changes below my branch
I'll hopefully be able to post later today or tomorrow.
My idea would be that my branch would replace ksmbd-for-next
and add your any my changes on top.
Thanks!
metze
Powered by blists - more mailing lists