From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "dgilbert@interlog.com" <dgilbert@interlog.com>,
"dvyukov@google.com" <dvyukov@google.com>
Cc: "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>,
"ben.hutchings@codethink.co.uk" <ben.hutchings@codethink.co.uk>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"syzkaller@googlegroups.com" <syzkaller@googlegroups.com>
Subject: Re: scsi: sg: assorted memory corruptions
Date: Mon, 22 Jan 2018 19:13:53 +0000 [thread overview]
Message-ID: <1516648432.2545.36.camel@wdc.com> (raw)
In-Reply-To: <CACT4Y+acm4hW05HCQTC03sEzY1oC4d4rOkfsYActEPmmnxyDRQ@mail.gmail.com>
On Mon, 2018-01-22 at 20:06 +0100, Dmitry Vyukov wrote:
> On Mon, Jan 22, 2018 at 7:57 PM, Douglas Gilbert <dgilbert@interlog.com> wrote:
> > As far as I remember, Dmitry has not indicated in multiple reports
> > over several years what /dev/sg0 is.
>
> That's because I know nothing about sg. If you give a command to run,
> I will provide it's output.
/dev/sg0 refers to a SCSI device. We would like to know the name of the SCSI
LLD driver. Would it be possible to provide the output of the following commands:
readlink /sys/class/scsi_generic/sg0
cat /sys/class/scsi_generic/sg0/device/vendor
Thanks,
Bart.
next prev parent reply other threads:[~2018-01-22 19:14 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 [this message]
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
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=1516648432.2545.36.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=ben.hutchings@codethink.co.uk \
--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