archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <>
To: Andreas Gruenbacher <>
Cc: Christoph Hellwig <>,
	"K.V, Aneesh" <>,
	cluster-devel <>,
	linux-fsdevel <>
Subject: Re: gfs2 iomap: BUG_ON(buffer_unmapped) in submit_bh_wbc
Date: Fri, 25 May 2018 14:24:24 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, May 24, 2018 at 08:25:55PM +0200, Andreas Gruenbacher wrote:
> Didn't get very far with your bh removal patches so far.

I think we could probably lift the whole XFS writeback code to iomap.c
once it stabilizes a little.  It just needs to use struct iomap
instead of the xfs-specific xfs_bmbt_irec, and the file system would
have to provide the map_blocks and end_io hooks.

      reply	other threads:[~2018-05-25 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 18:05 gfs2 iomap: BUG_ON(buffer_unmapped) in submit_bh_wbc Andreas Gruenbacher
2018-05-24 18:13 ` Christoph Hellwig
2018-05-24 18:25   ` Andreas Gruenbacher
2018-05-25 12:24     ` Christoph Hellwig [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).