Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1524482

Re: linux-next: manual merge of the block tree with the btrfs-kdave tree

From Christoph Hellwig <hch@lst.de>
Newsgroups linux.kernel
Subject Re: linux-next: manual merge of the block tree with the btrfs-kdave tree
Date 2016-11-17 18:10 +0100
Message-ID <sEymd-3v8-29@gated-at.bofh.it> (permalink)
References <sEkjg-2JC-13@gated-at.bofh.it> <sEkVX-30x-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Nov 16, 2016 at 07:49:29PM -0700, Jens Axboe wrote:
> doesn't look correct, if bio_readpage_error() is called from the 
> ->bi_end_io() handler. bi_size is generally zeroed at that time.

At least some of these bios are magic btrfs-internal ones that never
reach the block layer.  But I don't think all are, and both the new
code and one of the old cases are broken.  David, can you drop
this one patch for now, and I'll restart the discussion on the
failfast behavior on the btrfs list?

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

linux-next: manual merge of the block tree with the btrfs-kdave  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-11-17 03:10 +0100
  Re: linux-next: manual merge of the block tree with the btrfs-kdave  tree Jens Axboe <axboe@kernel.dk> - 2016-11-17 03:50 +0100
    Re: linux-next: manual merge of the block tree with the         btrfs-kdave tree Christoph Hellwig <hch@lst.de> - 2016-11-17 18:10 +0100
      Re: linux-next: manual merge of the block tree with the btrfs-kdave  tree David Sterba <dsterba@suse.cz> - 2016-11-18 18:50 +0100

csiph-web