>
> Hi Jean-Marie,
> it looks rather like drivers/char/n_tty.c doesn't bother to check the return
> value from put_user(). It's called three times in the file and none of the
> calls check the return value. I suspect checking and propagating the return
> value would fix this. In any case, no data should be transferred so it's only
> the return status that's bad, rather than any actual corruption.
>
Indeed, this code is bogus! Personnally this does not bother me, and afterall
isn't 0 a valid address in ELF? The bottom of the stack? Be unfortunate to
have such a big stack! Anyway I do love big stacks.
