From: Jens Axboe <axboe@kernel.dk>
To: kernel test robot <oliver.sang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ltp@lists.linux.it,
linux-btrfs@vger.kernel.org
Subject: Re: [btrfs] 3d6ef82805: WARNING:at_fs/btrfs/extent-tree.c:#btrfs_reserve_extent[btrfs]
Date: Mon, 15 Feb 2021 08:40:02 -0700 [thread overview]
Message-ID: <8fec3d91-fd37-0159-7417-0661659e2e02@kernel.dk> (raw)
In-Reply-To: <20210215132734.GA15834@xsang-OptiPlex-9020>
On 2/15/21 6:27 AM, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: 3d6ef82805958611e8ffa0a901c014b6f066c3e6 ("btrfs: relax memory alignment restriction for O_DIRECT")
> https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-block.git dio-mem-align
This patch has been dropped, we did identify last week that btrfs
needs more work to support sub bs memory alignment for dio.
--
Jens Axboe
prev parent reply other threads:[~2021-02-15 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 13:27 [btrfs] 3d6ef82805: WARNING:at_fs/btrfs/extent-tree.c:#btrfs_reserve_extent[btrfs] kernel test robot
2021-02-15 15:40 ` Jens Axboe [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:
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=8fec3d91-fd37-0159-7417-0661659e2e02@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=oliver.sang@intel.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 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).