[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2103302221590.18977@angie.orcam.me.uk>
Date: Tue, 30 Mar 2021 22:31:45 +0200 (CEST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Palmer Dabbelt <palmer@...belt.com>
cc: alex@...ti.fr, Paul Walmsley <paul.walmsley@...ive.com>,
dvyukov@...gle.com, linux-api@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: Bump COMMAND_LINE_SIZE value to 1024
On Mon, 29 Mar 2021, Palmer Dabbelt wrote:
> > --- /dev/null
> > +++ b/arch/riscv/include/uapi/asm/setup.h
> > @@ -0,0 +1,8 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
> > +
> > +#ifndef _UAPI_ASM_RISCV_SETUP_H
> > +#define _UAPI_ASM_RISCV_SETUP_H
> > +
> > +#define COMMAND_LINE_SIZE 1024
> > +
> > +#endif /* _UAPI_ASM_RISCV_SETUP_H */
>
> I put this on fixes, but it seemes like this should really be a Kconfig
> enttry. Either way, ours was quite a bit smaller than most architectures and
> it's great that syzbot has started to find bugs, so I'd rather get this in
> sooner.
This macro is exported as a part of the user API so it must not depend on
Kconfig. Also changing it (rather than say adding COMMAND_LINE_SIZE_V2 or
switching to an entirely new data object that has its dimension set in a
different way) requires careful evaluation as external binaries have and
will have the value it expands to compiled in, so it's a part of the ABI
too.
Maciej
Powered by blists - more mailing lists