From: Omar Sandoval <osandov@osandov.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>,
linux-btrfs@vger.kernel.org
Subject: Re: BTRFS warning (device dm-0): unhandled fiemap cache detected
Date: Mon, 21 Aug 2017 11:30:37 -0700 [thread overview]
Message-ID: <20170821183037.GA16030@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <ff53b205-4bdd-a360-91d7-068b65b23dad@gmx.com>
On Mon, Aug 21, 2017 at 11:31:34AM +0800, Qu Wenruo wrote:
>
>
> On 2017年08月21日 11:27, Christoph Anton Mitterer wrote:
> > On Mon, 2017-08-21 at 10:43 +0800, Qu Wenruo wrote:
> > > Harmless, it is only designed to merge fiemap output.
> > Thanks for the info :)
> >
> >
> > On Mon, 2017-08-21 at 10:57 +0800, Qu Wenruo wrote:
> > > Quite strange, according to upstream git log, that commit is merged
> > > between v4.12-rc7 and v4.12.
> > > Maybe I misunderstand the stable kernel release cycle.
> >
> > Seems it was only added in 4.12.7? Maybe a typo?
>
> I'm talking about upstream, which is managed by Linus.
> The 4.12.x is managed by maintainers of stable releases.
>
> In Linus repo, the commit is between v4.12 and v4.12-rc7 tag.
> Maybe v4.12.x is started before v4.12 release.
It's not in 4.12.
$ git tag --contains 848c23b78fafdcd3270b06a30737f8dbd70c347f
for-4.13-part2-tag
v4.13-rc1
v4.13-rc2
v4.13-rc3
v4.13-rc4
v4.13-rc5
prev parent reply other threads:[~2017-08-21 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 2:29 BTRFS warning (device dm-0): unhandled fiemap cache detected Christoph Anton Mitterer
2017-08-21 2:43 ` Qu Wenruo
2017-08-21 2:57 ` Qu Wenruo
2017-08-21 3:27 ` Christoph Anton Mitterer
2017-08-21 3:31 ` Qu Wenruo
2017-08-21 18:30 ` Omar Sandoval [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=20170821183037.GA16030@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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.