From: "Darrick J. Wong" <djwong@kernel.org>
To: cem@kernel.org
Cc: aalbersh@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v4 2/2] fsr: always print error messages from xfrog_defragrange()
Date: Tue, 7 Apr 2026 08:07:08 -0700 [thread overview]
Message-ID: <20260407150708.GE1048989@frogsfrogsfrogs> (raw)
In-Reply-To: <20260407111507.79977-3-cem@kernel.org>
On Tue, Apr 07, 2026 at 01:15:00PM +0200, cem@kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> Error messages from xfrog_defragrange() are only printed when
> verbose/debug flags are used.
>
> We had reports from users complaining it's hard to find out the error
> messages lost in the middle of dozens of other informational messages.
>
> Change packfile() behavior to print errors independently of verbose or
> debug flags.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
Looks ok,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
>
> V4: fix up previous rebase (fprintf accidentally removed)
> V3: Rebase on top of patch 1 changes
> V2: Update commit description
>
> fsr/xfs_fsr.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/fsr/xfs_fsr.c b/fsr/xfs_fsr.c
> index 390f7c5276df..e74180c143be 100644
> --- a/fsr/xfs_fsr.c
> +++ b/fsr/xfs_fsr.c
> @@ -1464,19 +1464,15 @@ packfile(
> case 0:
> break;
> case ENOTSUP:
> - if (vflag || dflag)
> - fsrprintf(_("%s: file type not supported\n"), fname);
> + fsrprintf(_("%s: file type not supported\n"), fname);
> break;
> case EFAULT:
> /* The file has changed since we started the copy */
> - if (vflag || dflag)
> - fsrprintf(_("%s: file modified defrag aborted\n"),
> - fname);
> + fsrprintf(_("%s: file modified defrag aborted\n"), fname);
> break;
> case EBUSY:
> /* Timestamp has changed or mmap'ed file */
> - if (vflag || dflag)
> - fsrprintf(_("%s: file busy\n"), fname);
> + fsrprintf(_("%s: file busy\n"), fname);
> break;
> default:
> fsrprintf(_("XFS_IOC_SWAPEXT failed: %s: %s\n"),
> --
> 2.53.0
>
>
prev parent reply other threads:[~2026-04-07 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 11:14 [PATCH v4 0/2] Improve user experience with xfs_fsr cem
2026-04-07 11:14 ` [PATCH v4 1/2] fsr: package function should check for negative errors cem
2026-04-07 11:15 ` [PATCH v4 2/2] fsr: always print error messages from xfrog_defragrange() cem
2026-04-07 15:07 ` Darrick J. Wong [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=20260407150708.GE1048989@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=cem@kernel.org \
--cc=linux-xfs@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