From: Andrew Morton <akpm@linux-foundation.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Grant Likely <grant.likely@linaro.org>,
Andi Kleen <ak@linux.intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC 1/2] lib: string: Remove duplicated function
Date: Thu, 11 Sep 2014 15:22:41 -0700 [thread overview]
Message-ID: <20140911152241.22ce7f1ebecef7ce7e01b112@linux-foundation.org> (raw)
In-Reply-To: <1409124962-11527-2-git-send-email-linux@rasmusvillemoes.dk>
On Wed, 27 Aug 2014 09:36:01 +0200 Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
> lib/string.c contains two functions, strnicmp and strncasecmp, which
> do roughly the same thing, namely compare two strings
> case-insensitively up to a given bound. They have slightly different
> implementations, but the only important difference is that strncasecmp
> doesn't handle len==0 appropriately; it effectively becomes strcasecmp
> in that case. strnicmp correctly says that two strings are always
> equal in their first 0 characters.
>
> strncasecmp is the POSIX name for this functionality. So rename the
> non-broken function to the standard name. To minimize the impact on
> the rest of the kernel (and since both are exported to modules), make
> strnicmp a wrapper for strncasecmp.
I guess it's safe to assume that nobody was depending on the
strncasecmp() bug.
The existing strnicmp() implementation is rather verbose, but I expect
that avoiding the tolower() cost where possible makes sense.
Yes, please prepare the strnicmp()->strncasecmp() patches and let's get
them merged up. After a kernel release or two we can zap the
back-compat wrapper.
And it isn't just "out of tree modules" that we should be concerned
about - we'll commonly find that "to be in tree" code is using
interfaces which we're trying to alter or remove, so it takes a cycle
or two to get everything propagated. Most of this code can be found in
linux-next.
next prev parent reply other threads:[~2014-09-11 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 7:36 [PATCH/RFC 0/2] " Rasmus Villemoes
2014-08-27 7:36 ` [PATCH/RFC 1/2] " Rasmus Villemoes
2014-09-11 22:22 ` Andrew Morton [this message]
2014-09-12 9:01 ` Rasmus Villemoes
2014-09-12 9:43 ` Joe Perches
2014-09-12 18:52 ` Tejun Heo
2014-08-27 7:36 ` [PATCH/RFC 2/2] lib: string: Make all calls to strnicmp into calls to strncasecmp Rasmus Villemoes
2014-08-27 9:05 ` Dan Carpenter
2014-08-27 9:13 ` Rasmus Villemoes
2014-08-27 10:17 ` Dan Carpenter
2014-08-30 18:11 ` Rasmus Villemoes
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=20140911152241.22ce7f1ebecef7ce7e01b112@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=grant.likely@linaro.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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
all inboxes | Powered by JetHome®