From: Stefano Brivio <sbrivio@redhat.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org, Ronnie Sahlberg <lsahlber@redhat.com>,
Jianhong Yin <jiyin@redhat.com>,
Pavel Shilovsky <pshilov@microsoft.com>,
Shirish Pargaonkar <shirishpargaonkar@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting
Date: Thu, 5 Jul 2018 16:58:58 +0200 [thread overview]
Message-ID: <20180705165858.7679fc44@epycfail> (raw)
In-Reply-To: <87d0w17nu3.fsf@suse.com>
On Thu, 05 Jul 2018 16:35:00 +0200
Aurélien Aptel <aaptel@suse.com> wrote:
> Stefano Brivio <sbrivio@redhat.com> writes:
> > /* BB eventually switch this to SMB2 specific small buf size */
> > - *request_buf = cifs_small_buf_get();
> > + if (smb2_command == SMB2_SET_INFO)
> > + *request_buf = cifs_buf_get();
> > + else
> > + *request_buf = cifs_small_buf_get();
> > if (*request_buf == NULL) {
> > /* BB should we add a retry in here if not a writepage? */
> > return -ENOMEM;
> > @@ -3720,7 +3723,7 @@ send_set_info(const unsigned int xid, struct cifs_tcon *tcon,
> >
> > rc = cifs_send_recv(xid, ses, &rqst, &resp_buftype, flags,
> > &rsp_iov);
> > - cifs_small_buf_release(req);
> > + cifs_buf_release(req);
> > rsp = (struct smb2_set_info_rsp *)rsp_iov.iov_base;
>
> Small and large bufs use different mempools, shouldn't the release func
> match the get func?
I think it does: for SMB2_SET_INFO we'll allocate with cifs_buf_get(),
which does:
ret_buf = mempool_alloc(cifs_req_poolp, GFP_NOFS);
and release with cifs_buf_release():
mempool_free(buf_to_free, cifs_req_poolp);
am I missing something?
--
Stefano
next prev parent reply other threads:[~2018-07-05 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 9:46 [PATCH] cifs: Fix slab-out-of-bounds in send_set_info() on SMB2 ACE setting Stefano Brivio
2018-07-05 14:35 ` Aurélien Aptel
2018-07-05 14:55 ` Steve French
2018-07-05 16:00 ` Stefano Brivio
2018-07-05 17:11 ` Aurélien Aptel
2018-07-05 14:58 ` Stefano Brivio [this message]
2018-07-05 16:05 ` Aurélien Aptel
2018-07-05 17:53 ` Steve French
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=20180705165858.7679fc44@epycfail \
--to=sbrivio@redhat.com \
--cc=aaptel@suse.com \
--cc=jiyin@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=pshilov@microsoft.com \
--cc=sfrench@samba.org \
--cc=shirishpargaonkar@gmail.com \
--cc=stable@vger.kernel.org \
/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).