From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: tytso@mit.edu, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, jaegeuk@kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2] libfs: Attempt exact-match comparison first during casefold lookup
Date: Thu, 18 Jan 2024 13:51:33 -0300 [thread overview]
Message-ID: <87y1cmega2.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <8734uufy1o.fsf@mailhost.krisman.be> (Gabriel Krisman Bertazi's message of "Thu, 18 Jan 2024 12:42:27 -0300")
Gabriel Krisman Bertazi <krisman@suse.de> writes:
> can't change since it's already a copy of the dentry->d_name pointer;
dentry->d_name.name
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2024-01-18 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 0:46 [PATCH v2] libfs: Attempt exact-match comparison first during casefold lookup Gabriel Krisman Bertazi
2024-01-18 3:50 ` Eric Biggers
2024-01-18 15:42 ` Gabriel Krisman Bertazi
2024-01-18 16:51 ` Gabriel Krisman Bertazi [this message]
2024-01-18 19:29 ` Linus Torvalds
2024-01-19 14:13 ` Gabriel Krisman Bertazi
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=87y1cmega2.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).