Re: strncpy optimalisation? (lib/string.c)

Willy Tarreau wrote:
> Original code completely pads the destination with zeroes,
> while yours only adds the last zero. Your code does what
> strncpy() is said to do, but maybe there's a particular
> reason for it to behave differently in the kernel

No, the kernel's strncpy() behaves the same as the one in libc.  Run
"man strncpy" if you don't believe me.

In the common case where you just want to copy a string and avoid
overflow use strlcpy() instead

-Mitch
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: strncpy optimalisation? (lib/string.c)
    • From: Folkert van Heusden <[email protected]>

• References:
  • strncpy optimalisation? (lib/string.c)
    • From: Folkert van Heusden <[email protected]>
  • Re: strncpy optimalisation? (lib/string.c)
    • From: Willy Tarreau <[email protected]>

• Prev by Date: optimalisation for strlcpy (lib/string.c)
• Next by Date: Re: strncpy optimalisation? (lib/string.c)
• Previous by thread: Re: strncpy optimalisation? (lib/string.c)
• Next by thread: Re: strncpy optimalisation? (lib/string.c)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]