James Bottomley <[email protected]> wrote:
>
> On Wed, 2005-08-10 at 10:05 -0700, Andrew Morton wrote:
> > Ingo Molnar <[email protected]> wrote:
> > > yeah ... cannot remember why i have done it originally :-|
>
> > Might it be to do with sizeof(task_struct.comm)?
>
> But that's 16 bytes not 10;
Well we stick a "/%d" at the end, which gets us up to 14 chars, assuming
NR_CPUS < 1000
> and anyway, it doesn't have to be unique;
> set_task_comm just does a strlcpy from the name, so it will be truncated
> (same as for a binary with > 15 character name).
Yup. But it'd be fairly silly to go adding the /%d, only to have it
truncated off again.
We could truncate the name before adding the CPU number, but it sounds
saner to just prevent anyone passing in excessively long names. Via
BUG_ON, say ;)
What's the actual problem?
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |