From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Tomas Henzl <thenzl@redhat.com>,
"Ewan D.Milne" <emilne@redhat.com>,
Andrea Gelmini <andrea.gelmini@gelma.net>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [lkp] [ses] 3417c1b5cb: WARNING: CPU: 2 PID: 2013 at fs/xfs/xfs_file.c:772 xfs_file_dio_aio_write+0x2a2/0x320()
Date: Sun, 27 Dec 2015 21:19:18 -0800 [thread overview]
Message-ID: <1451279958.2283.4.camel@HansenPartnership.com> (raw)
In-Reply-To: <87ziwv2vrp.fsf@yhuang-dev.intel.com>
[cc to linux-scsi added]
On Mon, 2015-12-28 at 09:43 +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ma
> ster
> commit 3417c1b5cb1fdc10261dbed42b05cc93166a78fd ("ses: Fix problems
> with simple enclosures")
>
> This may be the intended behavior, we found after your commit, the
> following new message appears in kernel log:
>
> [ 40.804515] scsi 8:0:12:0: Wrong diagnostic page; asked for 7 got
> 0
>
> To reproduce:
>
> git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this
> email
> bin/lkp run job.yaml
OK, so what is the enclosure device at host 8? And what happens when
you use sg_ses to ask for page 7?
James
next parent reply other threads:[~2015-12-28 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ziwv2vrp.fsf@yhuang-dev.intel.com>
2015-12-28 5:19 ` James Bottomley [this message]
[not found] ` <87bn9b0zjh.fsf@yhuang-dev.intel.com>
2015-12-29 2:11 ` [LKP] [lkp] [ses] 3417c1b5cb: WARNING: CPU: 2 PID: 2013 at fs/xfs/xfs_file.c:772 xfs_file_dio_aio_write+0x2a2/0x320() James Bottomley
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=1451279958.2283.4.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=andrea.gelmini@gelma.net \
--cc=emilne@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@01.org \
--cc=thenzl@redhat.com \
--cc=ying.huang@linux.intel.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