From: Markus Elfring <Markus.Elfring@web.de>
To: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
Aurelien Aptel <aaptel@suse.com>,
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>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/3] smb: client: Better exception handling for SMB3 hash allocations
Date: Fri, 10 Oct 2025 08:45:14 +0200 [thread overview]
Message-ID: <e8a44f5e-0f29-40ab-a6a3-74802cd970aa@web.de> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 10 Oct 2025 08:40:08 +0200
Refine a few implementation details for further development considerations.
Markus Elfring (3):
Return directly after a failed cifs_alloc_hash()
in smb3_crypto_shash_allocate()
Improve resource release
in smb311_crypto_shash_allocate()
Omit a variable initialisation
in smb311_crypto_shash_allocate()
fs/smb/client/smb2transport.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-10 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 6:45 Markus Elfring [this message]
2025-10-10 6:48 ` [PATCH 1/3] smb: client: Return directly after a failed cifs_alloc_hash() in smb3_crypto_shash_allocate() Markus Elfring
2025-10-10 6:50 ` [PATCH 2/3] smb: client: Improve resource release in smb311_crypto_shash_allocate() Markus Elfring
2025-10-10 6:51 ` [PATCH 3/3] smb: client: Omit a variable initialisation " Markus Elfring
2025-10-10 21:47 ` Steve French
2025-10-12 9:44 ` [0/3] smb: client: Better exception handling for SMB3 hash allocations 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=e8a44f5e-0f29-40ab-a6a3-74802cd970aa@web.de \
--to=markus.elfring@web.de \
--cc=aaptel@suse.com \
--cc=bharathsm@microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sfrench@samba.org \
--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
all inboxes | Powered by JetHome®