From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Kashyap Desai <kashyap.desai@broadcom.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: out of range LBA using sg_raw
Date: Wed, 08 Mar 2017 19:40:30 -0500 [thread overview]
Message-ID: <yq1d1dr1dvl.fsf@oracle.com> (raw)
In-Reply-To: <07493b3c3da0b19a9fa96899cad640f3@mail.gmail.com> (Kashyap Desai's message of "Wed, 8 Mar 2017 22:19:58 +0530")
>>>>> "Kashyap" == Kashyap Desai <kashyap.desai@broadcom.com> writes:
Kashyap,
Kashyap> Agree on this point. I am planning to study all possible such
Kashyap> sanity in driver for VD and not trying to fix one specific
Kashyap> scenario as described here. Do you think fix in this area is
Kashyap> good for kernel-stable as well OR just keep in linux-next as it
Kashyap> is not so severe considering real time exposure ? Trying to
Kashyap> understand priority and severity of this issue.
Since you're presumably only handling reads and writes in the fast path,
I assume the sanity checking will be fairly simple and thus a candidate
for stable.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-03-09 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 14:21 out of range LBA using sg_raw Kashyap Desai
2017-03-08 15:11 ` Christoph Hellwig
2017-03-08 15:59 ` Kashyap Desai
2017-03-08 16:04 ` Bart Van Assche
2017-03-08 16:15 ` Kashyap Desai
2017-03-08 16:06 ` Christoph Hellwig
2017-03-08 16:11 ` Kashyap Desai
2017-03-08 16:32 ` Martin K. Petersen
2017-03-08 16:49 ` Kashyap Desai
2017-03-09 0:40 ` Martin K. Petersen [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=yq1d1dr1dvl.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hch@infradead.org \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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