From: Pavel Shilovsky <piastryyy@gmail.com>
To: Aurelien Aptel <aaptel@suse.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
Steve French <smfrench@gmail.com>
Subject: Re: [PATCH] cifs: fix channel signing
Date: Thu, 6 Feb 2020 10:20:23 -0800 [thread overview]
Message-ID: <CAKywueQP9sUQx6OtEAETkH=X2ewthf3CZ6qyLiL+pV-MLxwMbA@mail.gmail.com> (raw)
In-Reply-To: <20200206124926.25376-1-aaptel@suse.com>
чт, 6 февр. 2020 г. в 05:00, Aurelien Aptel <aaptel@suse.com>:
>
> The server var was accidentally used as an iterator over the global
> list of connections, thus overwritten the passed argument. This
> resulted in the wrong signing key being returned for extra channels.
>
> Fix this by using a separate var to iterate.
>
> Signed-off-by: Aurelien Aptel <aaptel@suse.com>
> ---
> fs/cifs/smb2transport.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/cifs/smb2transport.c b/fs/cifs/smb2transport.c
> index fe6acfce3390..08b703b7a15e 100644
> --- a/fs/cifs/smb2transport.c
> +++ b/fs/cifs/smb2transport.c
> @@ -104,13 +104,14 @@ int smb2_get_sign_key(__u64 ses_id, struct TCP_Server_Info *server, u8 *key)
> {
> struct cifs_chan *chan;
> struct cifs_ses *ses = NULL;
> + struct TCP_Server_Info *it = NULL;
> int i;
> int rc = 0;
>
> spin_lock(&cifs_tcp_ses_lock);
>
> - list_for_each_entry(server, &cifs_tcp_ses_list, tcp_ses_list) {
> - list_for_each_entry(ses, &server->smb_ses_list, smb_ses_list) {
> + list_for_each_entry(it, &cifs_tcp_ses_list, tcp_ses_list) {
> + list_for_each_entry(ses, &it->smb_ses_list, smb_ses_list) {
> if (ses->Suid == ses_id)
> goto found;
> }
Good catch!
Reviewed-by: Pavel Shilovsky <pshilov@microsoft.com>
Stable candidate?
--
Best regards,
Pavel Shilovsky
prev parent reply other threads:[~2020-02-06 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 12:49 [PATCH] cifs: fix channel signing Aurelien Aptel
2020-02-06 18:20 ` Pavel Shilovsky [this message]
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='CAKywueQP9sUQx6OtEAETkH=X2ewthf3CZ6qyLiL+pV-MLxwMbA@mail.gmail.com' \
--to=piastryyy@gmail.com \
--cc=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=smfrench@gmail.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;
as well as URLs for NNTP newsgroup(s).