From: Fredric Cover <fredric.cover.lkernel@gmail.com>
To: Paulo Alcantara <pc@manguebit.org>, Namjae Jeon <linkinjeon@kernel.org>
Cc: ChenXiaoSong <chenxiaosong@chenxiaosong.com>,
Tom Talpey <tom@talpey.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Bharath SM <bharathsm@microsoft.com>,
linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org,
Fredric Cover <fredric.cover.lkernel@gmail.com>
Subject: [PATCH 0/2] smb: client: improve copy_ref_data() robustness
Date: Wed, 26 Aug 2026 12:10:31 -0700 [thread overview]
Message-ID: <20260826191033.162320-1-fredric.cover.lkernel@gmail.com> (raw)
1. Avoid setting the metadata of the cache
before updating the cache.
2. Harden copy_ref_data() against an empty ref
array.
Fredric Cover (2):
smb: client: fill cache fields after populating cache in
copy_ref_data()
smb: client: prevent out-of-bounds dfs_info3_param access in
copy_ref_data()
fs/smb/client/dfs_cache.c | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)
--
2.53.0
next reply other threads:[~2026-08-26 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 19:10 Fredric Cover [this message]
2026-08-26 19:10 ` [PATCH 1/2] smb: client: fill cache fields after populating cache in copy_ref_data() Fredric Cover
2026-09-02 16:55 ` Paulo Alcantara
2026-08-26 19:10 ` [PATCH 2/2] smb: client: prevent out-of-bounds dfs_info3_param access " Fredric Cover
2026-09-02 17:35 ` Paulo Alcantara
[not found] ` <notmuch-sha1-3e5d257ab3acfa72da7284e13dd0c817fac4b88c>
2026-09-02 17:48 ` Paulo Alcantara
2026-09-02 23:56 ` Fredric Cover
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=20260826191033.162320-1-fredric.cover.lkernel@gmail.com \
--to=fredric.cover.lkernel@gmail.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.