[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f5c25d6-ca8f-1e6d-b451-9f9074056cb0@collabora.com>
Date: Wed, 5 Oct 2022 10:17:36 +0500
From: Muhammad Usama Anjum <usama.anjum@...labora.com>
To: Paulo Alcantara <pc@....nz>, Steve French <sfrench@...ba.org>,
Ronnie Sahlberg <lsahlber@...hat.com>,
Shyam Prasad N <sprasad@...rosoft.com>,
Tom Talpey <tom@...pey.com>
Cc: kernel@...labora.com, kernel-janitors@...r.kernel.org,
linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] cifs: check returned value for error
On 10/5/22 12:01 AM, Paulo Alcantara wrote:
> Muhammad Usama Anjum <usama.anjum@...labora.com> writes:
>
>> smb311_decode_neg_context() can return error. Its return value should be
>> checked for errors.
>>
>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@...labora.com>
>> ---
>> fs/cifs/smb2pdu.c | 7 +++++--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/cifs/smb2pdu.c b/fs/cifs/smb2pdu.c
>> index 2bf43c892ae6..c6e37352dbe1 100644
>
> This patch doesn't apply in Steve's for-next branch[1]. If it still
> makes sense, please rebase and resend.
>
> [1] git://git.samba.org/sfrench/cifs-2.6.git
I've just applied on the latest next next-20221004 tag. This patch
doesn't apply. It seems some other patch has merged and this patch isn't
needed.
Can you apply only the first patch "[PATCH 1/2] cifs: remove
initialization value" from this series? Or should I send that only as v2?
Powered by blists - more mailing lists