From: Fengguang Wu <fengguang.wu@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Nicholas Bellinger <nab@linux-iscsi.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [scsi] WARNING: at fs/sysfs/dir.c:530 sysfs_add_one()
Date: Thu, 13 Jun 2013 10:44:27 +0800 [thread overview]
Message-ID: <20130613024427.GA11085@localhost> (raw)
In-Reply-To: <1371090883.1978.61.camel@dabdike>
On Wed, Jun 12, 2013 at 07:34:43PM -0700, James Bottomley wrote:
> On Thu, 2013-06-13 at 09:30 +0800, Fengguang Wu wrote:
> > Greetings,
> >
> > I got the below dmesg and the first bad commit is
> >
> > commit a256ba092ec57213f96059d41ac5473ff92f5e7c
> > Author: Nicholas Bellinger <nab@linux-iscsi.org>
> > Date: Sat May 18 02:40:43 2013 -0700
> >
> > scsi: Split scsi_dispatch_cmd into __scsi_dispatch_cmd setup
> >
> > Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
>
> You may be evaluating a bogus branch because no such commit has darkened
> the SCSI list, so it obviously can't be on upstream track.
Yeah, sorry I should probably not CC linux-scsi.
The bug is still in a private tree:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git scsi-mq
Thanks,
Fengguang
prev parent reply other threads:[~2013-06-13 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 1:30 [scsi] WARNING: at fs/sysfs/dir.c:530 sysfs_add_one() Fengguang Wu
2013-06-13 1:47 ` [__blk_mq_run_hw_queue] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Fengguang Wu
2013-06-13 2:34 ` [scsi] WARNING: at fs/sysfs/dir.c:530 sysfs_add_one() James Bottomley
2013-06-13 2:44 ` Fengguang Wu [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=20130613024427.GA11085@localhost \
--to=fengguang.wu@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.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).