From: Linus Torvalds <torvalds@linux-foundation.org>
To: Qu Wenruo <wqu@suse.com>
Cc: dsterba@suse.cz, David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs fixes for 6.8-rc2
Date: Fri, 26 Jan 2024 14:02:30 -0800 [thread overview]
Message-ID: <CAHk-=wj1h8GhhEuqmiCMZW7iBu3k7hn3mJSO9kTm7P31BCZExA@mail.gmail.com> (raw)
In-Reply-To: <7c4bc81e-51b4-4b93-8cae-f16663b1c820@suse.com>
On Fri, 26 Jan 2024 at 13:56, Qu Wenruo <wqu@suse.com> wrote:
>
> On 2024/1/27 08:21, Linus Torvalds wrote:
> >
> > Allocation lifetime problems?
>
> Could be, thus it may be better to output the flags of the first page
> for tree-checker.
Note that the fact that it magically went away certainly implies that
it never "really" existed, and that something was using a pointer or
similar.
IOW, this is not some IO that got scribbled over, or a cache that got
corrupted. If it had been real corruption, I would have expected that
it would have stayed around in memory.
Linus
next prev parent reply other threads:[~2024-01-26 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:33 [GIT PULL] Btrfs fixes for 6.8-rc2 David Sterba
2024-01-22 21:44 ` pr-tracker-bot
2024-01-22 22:34 ` Linus Torvalds
2024-01-22 22:54 ` Linus Torvalds
2024-01-22 23:01 ` Linus Torvalds
2024-01-22 23:05 ` David Sterba
2024-01-22 23:27 ` Qu Wenruo
2024-01-26 19:25 ` Linus Torvalds
2024-01-26 20:00 ` David Sterba
2024-01-26 21:39 ` Qu Wenruo
2024-01-26 21:51 ` Linus Torvalds
2024-01-26 21:56 ` Qu Wenruo
2024-01-26 22:02 ` Linus Torvalds [this message]
2024-01-26 22:05 ` Qu Wenruo
2024-01-26 21:05 ` 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='CAHk-=wj1h8GhhEuqmiCMZW7iBu3k7hn3mJSO9kTm7P31BCZExA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wqu@suse.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).