From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Li Bin <huawei.libin@huawei.com>
Cc: <dgilbert@interlog.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <xiexiuqi@huawei.com>
Subject: Re: [PATCH] scsi: sg: add sg_remove_request in sg_common_write
Date: Mon, 13 Apr 2020 21:59:14 -0400 [thread overview]
Message-ID: <yq1a73eu8st.fsf@oracle.com> (raw)
In-Reply-To: <1586777361-17339-1-git-send-email-huawei.libin@huawei.com> (Li Bin's message of "Mon, 13 Apr 2020 19:29:21 +0800")
Li,
> If the dxfer_len is greater than 256M that the request is invalid,
> it should call sg_remove_request in sg_common_write.
Applied to 5.7/scsi-fixes with a tweak to the commit description. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-04-14 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 11:29 [PATCH] scsi: sg: add sg_remove_request in sg_common_write Li Bin
2020-04-14 1:17 ` Douglas Gilbert
2020-04-14 1:59 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-13 11:28 Li Bin
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=yq1a73eu8st.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dgilbert@interlog.com \
--cc=huawei.libin@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xiexiuqi@huawei.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