From: David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Two more ib_srp patches
Date: Fri, 17 Aug 2012 11:07:36 -0400 [thread overview]
Message-ID: <1345216056.17811.7.camel@frustration.ornl.gov> (raw)
In-Reply-To: <502E13DA.2030603-HInyCGIudOg@public.gmane.org>
On Fri, 2012-08-17 at 05:50 -0400, Bart Van Assche wrote:
> Hello Dave,
>
> I think I have found two additional (longstanding) ib_srp issues. Do the
> patches below make sense to you ? If so, do you prefer that I post these
> as individual patches or that I merge these in the patch called "[PATCH
> 01/20] ib_srp: Fix a race condition" ?
Separate patches are fine.
> [PATCH 1/2] ib_srp: Fix use-after-free in srp_reset_req()
This needs to have a commit message along the lines of
"srp_free_req() uses the scsi_cmnd structure to unmap buffers, so we
must do that before we call release ownership by calling scsi_done()."
But otherwise
Acked-by: David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
> [PATCH 2/2] ib_srp: Avoid that aborted requests cause I/O to hang
Acked-by: David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
--
Dave Dillow
National Center for Computational Science
Oak Ridge National Laboratory
(865) 241-6602 office
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-17 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 9:50 Two more ib_srp patches Bart Van Assche
[not found] ` <502E13DA.2030603-HInyCGIudOg@public.gmane.org>
2012-08-17 15:07 ` David Dillow [this message]
[not found] ` <1345216056.17811.7.camel-zHLflQxYYDO4Hhoo1DtQwJ9G+ZOsUmrO@public.gmane.org>
2012-08-17 16:49 ` Roland Dreier
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=1345216056.17811.7.camel@frustration.ornl.gov \
--to=dillowda-1heg1yxhbw8@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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