[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220726083929.1684-1-tiwai@suse.de>
Date: Tue, 26 Jul 2022 10:39:24 +0200
From: Takashi Iwai <tiwai@...e.de>
To: linux-fsdevel@...r.kernel.org
Cc: Namjae Jeon <linkinjeon@...nel.org>,
Sungjong Seo <sj1557.seo@...sung.com>,
Petr Vorel <pvorel@...e.cz>, Joe Perches <joe@...ches.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/5] exfat: Fixes for ENAMETOOLONG error handling
Hi,
this is a revised series for fixing the error code of rename syscall
as well as cleanup / suppress the superfluous error messages.
As an LTP test case reported, exfat returns the inconsistent error
code for the case of renaming oversized file names:
https://bugzilla.suse.com/show_bug.cgi?id=1201725
The first patch fixes this inconsistency.
The second patch is just for correcting the definitions as bit flags,
and the remaining two patches are for suppressing the error message
that can be triggered too easily to debug messages.
thanks,
Takashi
===
v1: https://lore.kernel.org/r/20220722142916.29435-1-tiwai@suse.de
v1->v2:
* Expand to pr_*() directly in exfat_*() macros
* Add a patch to drop superfluous newlines in error messages
===
Takashi Iwai (5):
exfat: Return ENAMETOOLONG consistently for oversized paths
exfat: Define NLS_NAME_* as bit flags explicitly
exfat: Expand exfat_err() and co directly to pr_*() macro
exfat: Downgrade ENAMETOOLONG error message to debug messages
exfat: Drop superfluous new line for error messages
fs/exfat/exfat_fs.h | 18 ++++++++++--------
fs/exfat/fatent.c | 2 +-
fs/exfat/misc.c | 17 -----------------
fs/exfat/namei.c | 2 +-
fs/exfat/nls.c | 4 ++--
fs/exfat/super.c | 4 ++--
6 files changed, 16 insertions(+), 31 deletions(-)
--
2.35.3
Powered by blists - more mailing lists