[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201107211148.31290.richard@nod.at>
Date: Thu, 21 Jul 2011 11:48:31 +0200
From: Richard Weinberger <richard@....at>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [uml-devel] [PATCH 09/10] um: Ajdust size of pid_buf
Am Donnerstag 21 Juli 2011, 11:38:11 schrieb Geert Uytterhoeven:
> On Thu, Jul 21, 2011 at 11:18, Richard Weinberger <richard@....at> wrote:
> > Linux can have pids up to 4*1024*1024.
> > To handle such huge numbers pid_buf needs to be larger.
> >
> > Reported-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> > Signed-off-by: Richard Weinberger <richard@....at>
> > ---
> > arch/um/drivers/harddog_user.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/um/drivers/harddog_user.c
> > b/arch/um/drivers/harddog_user.c index b56f8e0..84dce3f 100644
> > --- a/arch/um/drivers/harddog_user.c
> > +++ b/arch/um/drivers/harddog_user.c
> > @@ -32,7 +32,7 @@ int start_watchdog(int *in_fd_ret, int *out_fd_ret,
> > char *sock) {
> > struct dog_data data;
> > int in_fds[2], out_fds[2], pid, n, err;
> > - char pid_buf[sizeof("nnnnn\0")], c;
> > + char pid_buf[sizeof("nnnnnnn\0")], c;
>
> Why not make it handle the full 32-bit? That's just a few bytes extra
> on the stack...
True.
The sizeof("nnnnnnn\0") crap will anyway go away.
ASAP I'll submit a patch which removes all sizeof("nnnnnnn\0") and replaces
sprintf() with snprintf().
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists