linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: linux-fsdevel@vger.kernel.org
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Sungjong Seo <sj1557.seo@samsung.com>,
	Petr Vorel <pvorel@suse.cz>, Joe Perches <joe@perches.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] exfat: Fixes for ENAMETOOLONG error handling
Date: Tue, 26 Jul 2022 10:39:24 +0200	[thread overview]
Message-ID: <20220726083929.1684-1-tiwai@suse.de> (raw)

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


             reply	other threads:[~2022-07-26  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  8:39 Takashi Iwai [this message]
2022-07-26  8:39 ` [PATCH v2 1/5] exfat: Return ENAMETOOLONG consistently for oversized paths Takashi Iwai
2022-07-26  8:39 ` [PATCH v2 2/5] exfat: Define NLS_NAME_* as bit flags explicitly Takashi Iwai
2022-07-26  8:39 ` [PATCH v2 3/5] exfat: Expand exfat_err() and co directly to pr_*() macro Takashi Iwai
2022-07-26  8:39 ` [PATCH v2 4/5] exfat: Downgrade ENAMETOOLONG error message to debug messages Takashi Iwai
2022-07-26  8:39 ` [PATCH v2 5/5] exfat: Drop superfluous new line for error messages Takashi Iwai
2022-07-29  3:08 ` [PATCH v2 0/5] exfat: Fixes for ENAMETOOLONG error handling Namjae Jeon

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=20220726083929.1684-1-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=joe@perches.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvorel@suse.cz \
    --cc=sj1557.seo@samsung.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).