All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: kernel BUG at block/bio.c:1787! while initializing scsi_debug on ppc64 host
Date: Tue, 5 Jan 2016 19:57:35 +0800	[thread overview]
Message-ID: <20160105115735.GA21068@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20151211115340.GB19209@eguan.usersys.redhat.com>

On Fri, Dec 11, 2015 at 07:53:40PM +0800, Eryu Guan wrote:
> Hi,
> 
> I saw this kernel BUG_ON on 4.4-rc4 kernel, and this can be reproduced
> easily on ppc64 host by:
> 
> modprobe scsi_debug sector_size=512 physblk_exp=3 dev_size_mb=256
> 
> And I bisected to this commit
> 
> 	commit ca369d51b3e1649be4a72addd6d6a168cfb3f537
> 	Author: Martin K. Petersen <martin.petersen@oracle.com>
> 	Date:   Fri Nov 13 16:46:48 2015 -0500
> 
> 	    block/sd: Fix device-imposed transfer length limits
> 
> I confirmed by reverting this commit on top of 4.4-rc4 kernel and test
> passed.

Hi,

Any updates on this? It's still reproducible with 4.4-rc8 kernel, and
still blocks some of my tests :)

Thanks,
Eryu

  parent reply	other threads:[~2016-01-05 11:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 12:01 kernel BUG at block/bio.c:1787! while initializing scsi_debug on ppc64 host Eryu Guan
2015-12-15 11:20 ` Eryu Guan
2015-12-15 12:06   ` Ming Lei
2015-12-15 13:06     ` Eryu Guan
2015-12-15 13:27       ` Ming Lei
2015-12-15 16:56         ` Eryu Guan
2015-12-16  1:15           ` Ming Lei
2015-12-16  1:39             ` Martin K. Petersen
2015-12-15 15:38       ` Ming Lei
2015-12-15 17:16         ` Eryu Guan
2015-12-15 18:29       ` Martin K. Petersen
2015-12-16  1:17         ` Ming Lei
2015-12-16  1:37           ` Martin K. Petersen
2015-12-16  7:25         ` Eryu Guan
2015-12-15 15:38   ` Martin K. Petersen
2016-01-05 11:57 ` Eryu Guan [this message]
2016-01-05 23:58   ` Martin K. Petersen
2016-01-06  3:33     ` Eryu Guan

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=20160105115735.GA21068@eguan.usersys.redhat.com \
    --to=guaneryu@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.