From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Dmitry Vyukov <dvyukov@google.com>, Doug Gilbert <dgilbert@interlog.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>
Subject: Re: scsi: sg: assorted memory corruptions
Date: Thu, 01 Feb 2018 16:17:39 +0000 [thread overview]
Message-ID: <1517501859.3417.67.camel@codethink.co.uk> (raw)
In-Reply-To: <CACT4Y+bObXrFiB0Qn+nfkD8DZRiVck1GJ5U9UeQz+-y85gh70Q@mail.gmail.com>
On Thu, 2018-02-01 at 08:04 +0100, Dmitry Vyukov wrote:
> On Thu, Feb 1, 2018 at 7:03 AM, Douglas Gilbert <dgilbert@interlog.com> wrote:
> > On 2018-01-30 07:22 AM, Dmitry Vyukov wrote:
[...]
> > > [1:0:0:0] cd/dvd QEMU QEMU DVD-ROM 2.0. /dev/sr0 /dev/sg1
> > >
> > > # readlink /sys/class/scsi_generic/sg0
> > >
> > > ../../devices/pci0000:00/0000:00:01.1/ata1/host0/target0:0:0/0:0:0:0/scsi_generic/sg0
> > >
> > > # cat /sys/class/scsi_generic/sg0/device/vendor
> > > ATA
> >
> >
> > ^^^^^
> > That subsystem is the culprit IMO, most likely libata.
> >
> > Until you can show this test failing on something other than an
> > ATA disk, then I will treat this issue as closed.
>
> Hi Doug,
>
> Why is bug in ATA not a bug? Is it long unused by everybody? I've got
> it by running qemu with default flags...
If the bug is in libata then it's not on Doug to fix it since he's only
maintaining sg.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-02-01 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 11:06 scsi: sg: assorted memory corruptions Dmitry Vyukov
2018-01-22 16:30 ` Bart Van Assche
2018-01-22 18:57 ` Douglas Gilbert
2018-01-22 19:06 ` Dmitry Vyukov
2018-01-22 19:13 ` Bart Van Assche
2018-01-30 12:22 ` Dmitry Vyukov
2018-02-01 6:03 ` Douglas Gilbert
2018-02-01 7:04 ` Dmitry Vyukov
2018-02-01 16:17 ` Ben Hutchings [this message]
2018-02-01 16:21 ` Dmitry Vyukov
2018-02-04 9:07 ` Eric Biggers
2018-02-04 11:10 ` Dmitry Vyukov
2018-02-10 19:13 ` Eric Biggers
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=1517501859.3417.67.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Bart.VanAssche@wdc.com \
--cc=dgilbert@interlog.com \
--cc=dvyukov@google.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzkaller@googlegroups.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