Re: [PATCH] Fix user data corrupted by old value return of sysctl



2005/12/31, Yi Yang <yang.y.yi@xxxxxxxxx>:
> Coywolf Qi Hunt wrote:
> >You didn't set the trailing '\0', I wonder how your printf did work
> >properly ever. You've just been lucky or something.
> >
> >-- Coywolf
> >
> >
> The variable target does it, its value is 0x00000001, so you mustn't
> worry it.
> osname only has 4-bytes space, so if you set '\0' to its tail, a byte
> information will be lost.

I'm worrying more. We should set '\0'. Let the one byte information
lost, the caller deserve that. Actually here printf sees "mylo"+'\01'
if little endian.

Linus, besides fixing bug, your commit certainly breaks userland
compatibility. Please consider.
--
Coywolf Qi Hunt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: The variable bit cpu
    ... > Euhm the above stuff about printf etc is too c library like specific, ... > lost me;) ... Then why are you posting in comp.lang.c? ...
    (comp.lang.c)
  • Re: probem with dl_runtime.c
    ... You didn't understand what gdb is telling you. ... > If it is not float, printf gets lost and barfs at return (see ... "printf to get lost", nor can this be the cause of a SIGSEGV. ... In order to understand recursion you must first understand recursion. ...
    (comp.os.linux.development.system)