From: Maxim Levitsky <mlevitsk@redhat.com>
To: "Max Reitz" <mreitz@redhat.com>,
"Dmitry Fomichev" <dmitry.fomichev@wdc.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Damien Le Moal <damien.lemoal@wdc.com>,
Alistair Francis <alistair.francis@wdc.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 1/2] file-posix: Correctly read max_segments of SG nodes
Date: Thu, 17 Sep 2020 16:22:59 +0300 [thread overview]
Message-ID: <ea4017fe0456a9c663f943f60f4572ecf8d0fe96.camel@redhat.com> (raw)
In-Reply-To: <808e395e-6f99-acdb-03dc-400f6bd32311@redhat.com>
On Thu, 2020-09-17 at 15:16 +0200, Max Reitz wrote:
> On 12.08.20 00:51, Dmitry Fomichev wrote:
> > If scsi-generic driver is in use, an SG node can be specified in
> > the command line in place of a regular SCSI device. In this case,
> > sg_get_max_segments() fails to open max_segments entry in sysfs
> > because /dev/sgX is a character device. As the result, the maximum
> > transfer size for the device may be calculated incorrectly, causing
> > I/O errors if the maximum transfer size at the guest ends up to be
> > larger compared to the host.
> >
> > Check system device type in sg_get_max_segments() and read the
> > max_segments value differently if it is a character device.
> >
> > Reported-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> > Fixes: 9103f1ceb46614b150bcbc3c9a4fbc72b47fedcc
> > Signed-off-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> > ---
> > block/file-posix.c | 55 +++++++++++++++++++++++++++-------------------
> > 1 file changed, 32 insertions(+), 23 deletions(-)
> >
> > diff --git a/block/file-posix.c b/block/file-posix.c
> > index 094e3b0212..f9e2424e8f 100644
> > --- a/block/file-posix.c
> > +++ b/block/file-posix.c
> > @@ -1108,6 +1108,7 @@ static int sg_get_max_segments(int fd)
> > int ret;
> > int sysfd = -1;
> > long max_segments;
> > + unsigned int max_segs;
> > struct stat st;
> >
> > if (fstat(fd, &st)) {
> > @@ -1115,30 +1116,38 @@ static int sg_get_max_segments(int fd)
> > goto out;
> > }
> >
> > - sysfspath = g_strdup_printf("/sys/dev/block/%u:%u/queue/max_segments",
> > - major(st.st_rdev), minor(st.st_rdev));
> > - sysfd = open(sysfspath, O_RDONLY);
> > - if (sysfd == -1) {
> > - ret = -errno;
> > - goto out;
> > + if (S_ISBLK(st.st_mode)) {
> > + sysfspath = g_strdup_printf("/sys/dev/block/%u:%u/queue/max_segments",
> > + major(st.st_rdev), minor(st.st_rdev));
>
> Sounds reasonable, but this function is (naturally) only called if
> bs->sg is true, which is set by hdev_is_sg(), which returns true only if
> the device file is a character device.
>
> So is this path ever taken, or can we just replace it all with the ioctl?
>
> (Before 867eccfed84, this function was used for all host devices, which
> might explain why the code even exists.)
>
> Max
I have another proposal which I am currently evaluating.
How about we drop all the SG_IO limits code alltogher from the raw driver, and
instead just let the scsi drivers (scsi-block and scsi-generic) query
the device directly, since I don't think that the kernel (I will double check this)?
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2020-09-17 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 22:51 [PATCH 0/2] block;scsi-generic: Fix max transfer size calculation Dmitry Fomichev
2020-08-11 22:51 ` [PATCH 1/2] file-posix: Correctly read max_segments of SG nodes Dmitry Fomichev
2020-09-17 13:16 ` Max Reitz
2020-09-17 13:22 ` Maxim Levitsky [this message]
2020-09-17 13:24 ` Maxim Levitsky
2020-09-17 16:44 ` Dmitry Fomichev
2020-09-19 15:18 ` Paolo Bonzini
2020-09-19 15:15 ` Paolo Bonzini
2020-08-11 22:51 ` [PATCH 2/2] scsi-generic: Fix HM-zoned device scan Dmitry Fomichev
2020-08-17 15:58 ` Alistair Francis
2020-08-17 16:38 ` [PATCH 0/2] block; scsi-generic: Fix max transfer size calculation Paolo Bonzini
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=ea4017fe0456a9c663f943f60f4572ecf8d0fe96.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).