From: Jim Meyering <jim@meyering.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] kmemleak: avoid buffer overrun: NUL-terminate strncpy-copied command
Date: Wed, 29 Aug 2012 08:28:47 +0200 [thread overview]
Message-ID: <874nnm6wkg.fsf@rho.meyering.net> (raw)
In-Reply-To: <20120828202459.GA13638@mwanda> (Dan Carpenter's message of "Tue, 28 Aug 2012 13:24:59 -0700")
Dan Carpenter wrote:
> On Fri, Aug 24, 2012 at 01:23:29PM +0200, Jim Meyering wrote:
>> In that case, what would you think of a patch to use strcpy instead?
>>
>> - strncpy(object->comm, current->comm, sizeof(object->comm));
>> + strcpy(object->comm, current->comm);
>
> Another option would be to use strlcpy(). It's slightly neater than
> the strncpy() followed by a NUL assignment.
>
>> Is there a preferred method of adding a static_assert-like statement?
>> I see compile_time_assert and a few similar macros, but I haven't
>> spotted anything that is used project-wide.
>
> BUILD_BUG_ON().
Hi Dan,
Thanks for the feedback and tip. How about this patch?
-- >8 --
Subject: [PATCH] kmemleak: remove unwarranted uses of strncpy
Use of strncpy was not justified -- was misleading, in fact, since
none of the three uses could trigger strncpy's truncation feature,
nor did they require the NUL-padding it can provide. Replace each
use with a BUG_ON_BUILD to ensure that the existing constraint
(source string is no larger than the size of the destination buffer)
and a use of strcpy. With the literals, it's easy to see that each
is shorter than TASK_COMM_LEN (aka, 16). In the third case, the
source and destination buffer have the same length, so there is no
possibility of truncation.
Signed-off-by: Jim Meyering <meyering@redhat.com>
---
mm/kmemleak.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/mm/kmemleak.c b/mm/kmemleak.c
index 45eb621..7359ffa 100644
--- a/mm/kmemleak.c
+++ b/mm/kmemleak.c
@@ -542,10 +542,12 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size,
/* task information */
if (in_irq()) {
object->pid = 0;
- strncpy(object->comm, "hardirq", sizeof(object->comm));
+ BUILD_BUG_ON(sizeof "hardirq" > sizeof(current->comm));
+ strcpy(object->comm, "hardirq");
} else if (in_softirq()) {
object->pid = 0;
- strncpy(object->comm, "softirq", sizeof(object->comm));
+ BUILD_BUG_ON(sizeof "softirq" > sizeof(current->comm));
+ strcpy(object->comm, "softirq");
} else {
object->pid = current->pid;
/*
@@ -554,7 +556,8 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size,
* dependency issues with current->alloc_lock. In the worst
* case, the command line is not correct.
*/
- strncpy(object->comm, current->comm, sizeof(object->comm));
+ BUILD_BUG_ON(sizeof (object->comm) > sizeof(current->comm));
+ strcpy(object->comm, current->comm);
}
/* kernel backtrace */
--
1.7.12.116.g31e0100
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-08-29 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1345481724-30108-1-git-send-email-jim@meyering.net>
2012-08-20 16:55 ` Jim Meyering
2012-08-24 10:27 ` Catalin Marinas
2012-08-24 11:23 ` Jim Meyering
2012-08-28 20:24 ` Dan Carpenter
2012-08-29 6:28 ` Jim Meyering [this message]
2012-08-29 15:56 ` Dan Carpenter
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=874nnm6wkg.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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