On Tue, Dec 11, 2018 at 01:20:30AM -0500, Dennis Zhou wrote:
> On Tue, Dec 11, 2018 at 11:22:18AM +0800, Ming Lei wrote:
> > On Tue, Dec 11, 2018 at 11:09 AM Dennis Zhou wrote:
> > >
> > > Hi Ming,
> > >
> > > On Tue, Dec 11, 2018 at 10:36:07AM +0800, Ming Lei wrote:
> > > > Hi Jens and Dennis,
>
On Tue, Dec 11, 2018 at 11:22:18AM +0800, Ming Lei wrote:
> On Tue, Dec 11, 2018 at 11:09 AM Dennis Zhou wrote:
> >
> > Hi Ming,
> >
> > On Tue, Dec 11, 2018 at 10:36:07AM +0800, Ming Lei wrote:
> > > Hi Jens and Dennis,
> > >
> > > Just found the following issue when testing for-4.21/block when
>
On Tue, Dec 11, 2018 at 11:09 AM Dennis Zhou wrote:
>
> Hi Ming,
>
> On Tue, Dec 11, 2018 at 10:36:07AM +0800, Ming Lei wrote:
> > Hi Jens and Dennis,
> >
> > Just found the following issue when testing for-4.21/block when
> > running stress io & device
> > remove on scsi_debug, and it should be c
Hi Ming,
On Tue, Dec 11, 2018 at 10:36:07AM +0800, Ming Lei wrote:
> Hi Jens and Dennis,
>
> Just found the following issue when testing for-4.21/block when
> running stress io & device
> remove on scsi_debug, and it should be caused by recent blkcg changes.
>
> [ 37.144330] sd 8:0:0:15: [sds]
Hi Jens and Dennis,
Just found the following issue when testing for-4.21/block when
running stress io & device
remove on scsi_debug, and it should be caused by recent blkcg changes.
[ 37.144330] sd 8:0:0:15: [sds] Synchronizing SCSI cache
[ 37.665644] BUG: unable to handle kernel NULL pointer
