From: Christoph Hellwig <hch@lst.de>
To: Anand Jain <anand.jain@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
dsterba@suse.com, linux-btrfs@vger.kernel.org, clm@fb.com,
josef@toxicpanda.com
Subject: Re: [PATCH] btrfs: move all btree initialization into btrfs_init_btree_inode
Date: Mon, 27 Feb 2023 14:39:12 +0100 [thread overview]
Message-ID: <20230227133912.GA16298@lst.de> (raw)
In-Reply-To: <02026707-320e-5c2d-b35e-23290dfc36cc@oracle.com>
Thanks Anand. The fix looks good to me. The error handling is a bit
confsing and hopefully we can get it fixed up eventually.
Just curious how you found the error as I didn't see anything in
xfstest runs.
next prev parent reply other threads:[~2023-02-27 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 18:10 [PATCH] btrfs: move all btree initialization into btrfs_init_btree_inode Christoph Hellwig
2023-02-20 8:17 ` Johannes Thumshirn
2023-02-20 20:19 ` David Sterba
2023-02-21 14:28 ` Christoph Hellwig
2023-02-21 14:51 ` David Sterba
2023-02-27 7:35 ` Anand Jain
2023-02-27 13:39 ` Christoph Hellwig [this message]
2023-02-27 18:41 ` David Sterba
2024-02-14 6:28 ` Qu Wenruo
2024-02-14 7:12 ` David Sterba
2024-02-14 8:32 ` Qu Wenruo
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=20230227133912.GA16298@lst.de \
--to=hch@lst.de \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox