From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: add root id output for direct IO error messages
Date: Wed, 28 May 2025 15:43:45 +0200 [thread overview]
Message-ID: <20250528134344.GD4037@twin.jikos.cz> (raw)
In-Reply-To: <af31c7ae4ba5c76d57527f5a774f3816f69b54d8.1747695628.git.wqu@suse.com>
On Tue, May 20, 2025 at 08:30:32AM +0930, Qu Wenruo wrote:
> When debugging a kernel warning caused by generic/475, the error
> messages from direct IO lacks the subvolume id, meanwhile th error
> messages from buffered IO contains both subvolume id and inode number.
>
> This makes debugging much harder to grasp which inode (and its
> subvolume) is causing the problem.
>
> Add the subvolume id for direct IO failure message.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2025-05-28 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 23:00 [PATCH] btrfs: add root id output for direct IO error messages Qu Wenruo
2025-05-21 8:01 ` Daniel Vacek
2025-05-28 13:43 ` David Sterba [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=20250528134344.GD4037@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@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