[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200520121000.GF520@jagdpanzerIV.localdomain>
Date: Wed, 20 May 2020 21:10:00 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Chenggang Wang <wangchenggang@...o.com>,
linux-kernel@...r.kernel.org, Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC PATCH 2/2] init: Allow multi-line output of kernel command
line
On (20/05/19 21:58), Joe Perches wrote:
[..]
> > Maybe we can
> > use here something rather random and much shorter instead. E.g.
> > 256 chars. Hmm. How
>
> min(some_max like 132/256, PRINTK_LOG_LINE_MAX)
>
> would work.
An alternative approach would be to do what we do in the
print_modules() (the list of modules which can definitely
be longer than 1K chars).
We can split command line in a loop - memchr(pos, ' ') - and
pr_cont() parts of the command line. pr_cont() has overflow
control and it flushes cont buffer before it overflows, so
we should not lose anything.
-ss
Powered by blists - more mailing lists