From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] Initialise mid_q_entry before putting it on the pending queue
Date: Wed, 11 Jul 2012 11:31:03 +0100 [thread overview]
Message-ID: <1342002663.4041.1.camel@localhost> (raw)
In-Reply-To: <CADT32e+C2GzUMYizadxnp4Qv=22FO6mihq5fJWu80r_kp0+Bvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, 2012-07-10 at 14:26 -0500, Shirish Pargaonkar wrote:
> On Tue, Jul 10, 2012 at 1:58 PM, Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> > A user reported a crash in cifs_demultiplex_thread() caused by an
> > incorrectly set mid_q_entry->callback() function. It appears that the
> > callback assignment made in cifs_call_async() was not flushed back to
> > memory suggesting that a memory barrier was required here. Changing the
> > code to make sure that the mid_q_entry structure was completely
> > initialised before it was added to the pending queue fixes the problem.
> >
> > Signed-off-by: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > ---
> > fs/cifs/transport.c | 20 ++++++++++----------
> > 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > diff --git a/fs/cifs/transport.c b/fs/cifs/transport.c
> > index 3097ee5..c5faf02 100644
> > --- a/fs/cifs/transport.c
> > +++ b/fs/cifs/transport.c
> > @@ -365,14 +365,10 @@ cifs_setup_async_request(struct TCP_Server_Info *server, struct kvec *iov,
> > if (mid == NULL)
> > return -ENOMEM;
> >
> > - /* put it on the pending_mid_q */
> > - spin_lock(&GlobalMid_Lock);
> > - list_add_tail(&mid->qhead, &server->pending_mid_q);
> > - spin_unlock(&GlobalMid_Lock);
> > -
> > rc = cifs_sign_smb2(iov, nvec, server, &mid->sequence_number);
> > if (rc)
> > - delete_mid(mid);
> > + DeleteMidQEntry(mid);
> > +
> > *ret_mid = mid;
>
> Looks correct. But just a thought, why bother assigning ret_mid
> a Deleted mid if rc is not null?
I did notice this line which was already set to do this when I wrote the
patch. Since it did not result in any error, I left it alone. I will
create another patch which cleans this bit of the code.
Sachin Prabhu
>
> > return rc;
> > }
> > @@ -407,17 +403,21 @@ cifs_call_async(struct TCP_Server_Info *server, struct kvec *iov,
> > mid->callback_data = cbdata;
> > mid->mid_state = MID_REQUEST_SUBMITTED;
> >
> > + /* put it on the pending_mid_q */
> > + spin_lock(&GlobalMid_Lock);
> > + list_add_tail(&mid->qhead, &server->pending_mid_q);
> > + spin_unlock(&GlobalMid_Lock);
> > +
> > +
> > cifs_in_send_inc(server);
> > rc = smb_sendv(server, iov, nvec);
> > cifs_in_send_dec(server);
> > cifs_save_when_sent(mid);
> > mutex_unlock(&server->srv_mutex);
> >
> > - if (rc)
> > - goto out_err;
> > + if (rc == 0)
> > + return 0;
> >
> > - return rc;
> > -out_err:
> > delete_mid(mid);
> > add_credits(server, 1);
> > wake_up(&server->request_q);
> > --
> > 1.7.10.4
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-07-11 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 18:58 [PATCH] Initialise mid_q_entry before putting it on the pending queue Sachin Prabhu
[not found] ` <1341946720-4980-1-git-send-email-sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-07-10 19:11 ` Jeff Layton
2012-07-10 19:26 ` Shirish Pargaonkar
[not found] ` <CADT32e+C2GzUMYizadxnp4Qv=22FO6mihq5fJWu80r_kp0+Bvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-11 10:31 ` Sachin Prabhu [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=1342002663.4041.1.camel@localhost \
--to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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