From: Dongsu Park <dongsu.park@profitbricks.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Ming Lei <tom.leiming@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
xfs@oss.sgi.com, Lukas Czerner <lczerner@redhat.com>,
Jeff Layton <jlayton@poochiereds.net>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: kernel BUG at drivers/block/virtio_blk.c:172!
Date: Thu, 13 Nov 2014 12:04:15 +0100 [thread overview]
Message-ID: <20141113110415.GB16906@gmail.com> (raw)
In-Reply-To: <5463A478.20603@kernel.dk>
On 12.11.2014 11:18, Jens Axboe wrote:
> On 11/11/2014 09:42 AM, Ming Lei wrote:
> > The attached patch should fix the problem, and hope it is the last one, :-)
>
> Dongsu and Jeff, any of you test this variant? I think this is the last
> one, at least I hope so as well...
Yes, I've just tested it again with the Ming's patch.
It passed a full cycle of xfstests: No crash, no particular regression.
The code in blk_recount_segments() seems to make sense too.
Thanks! ;-)
Dongsu
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dongsu Park <dongsu.park@profitbricks.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Dave Chinner <david@fromorbit.com>,
xfs@oss.sgi.com, Lukas Czerner <lczerner@redhat.com>,
Jeff Layton <jlayton@poochiereds.net>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: kernel BUG at drivers/block/virtio_blk.c:172!
Date: Thu, 13 Nov 2014 12:04:15 +0100 [thread overview]
Message-ID: <20141113110415.GB16906@gmail.com> (raw)
In-Reply-To: <5463A478.20603@kernel.dk>
On 12.11.2014 11:18, Jens Axboe wrote:
> On 11/11/2014 09:42 AM, Ming Lei wrote:
> > The attached patch should fix the problem, and hope it is the last one, :-)
>
> Dongsu and Jeff, any of you test this variant? I think this is the last
> one, at least I hope so as well...
Yes, I've just tested it again with the Ming's patch.
It passed a full cycle of xfstests: No crash, no particular regression.
The code in blk_recount_segments() seems to make sense too.
Thanks! ;-)
Dongsu
next prev parent reply other threads:[~2014-11-13 11:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 13:04 kernel BUG at drivers/block/virtio_blk.c:172! Jeff Layton
2014-11-10 9:59 ` Rusty Russell
2014-11-10 9:59 ` Rusty Russell
2014-11-10 23:31 ` Jens Axboe
2014-11-10 23:31 ` Jens Axboe
2014-11-11 0:56 ` Ming Lei
2014-11-11 15:42 ` Dongsu Park
2014-11-11 15:42 ` Dongsu Park
2014-11-11 16:42 ` Ming Lei
2014-11-11 16:42 ` Ming Lei
2014-11-12 18:18 ` Jens Axboe
2014-11-12 18:18 ` Jens Axboe
2014-11-12 21:02 ` Jeff Layton
2014-11-12 21:02 ` Jeff Layton
2014-11-13 11:04 ` Dongsu Park [this message]
2014-11-13 11:04 ` Dongsu Park
2014-11-11 0:56 ` Ming Lei
-- strict thread matches above, loose matches on Subject: below --
2014-11-07 13:04 Jeff Layton
2015-10-01 1:10 Thomas D.
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=20141113110415.GB16906@gmail.com \
--to=dongsu.park@profitbricks.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jlayton@poochiereds.net \
--cc=lczerner@redhat.com \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tom.leiming@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xfs@oss.sgi.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.