linux-kernel - Re: Would you help to tell why async printk solution was not taken to upstream kernel ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <32058cbd-7d09-4316-afd9-c2f031a2a406.qixuan.wu@linux.alibaba.com>
Date:   Mon, 05 Mar 2018 14:56:59 +0800
From:   "Qixuan.Wu" <qixuan.wu@...ux.alibaba.com>
To:     "Steven Rostedt" <rostedt@...dmis.org>
Cc:     "linux-kernel-owner" <linux-kernel-owner@...r.kernel.org>,
        "Petr Mladek" <pmladek@...e.com>, "Jan Kara" <jack@...e.cz>,
        "Sergey Senozhatsky" <sergey.senozhatsky@...il.com>,
        "Sergey Senozhatsky" <sergey.senozhatsky.work@...il.com>,
        "linux-kernel" <linux-kernel@...r.kernel.org>,
        "chenggang.qin" <chenggang.qin@...ux.alibaba.com>,
        "caijingxian" <caijingxian@...ux.alibaba.com>,
        "yuanliang.wyl" <yuanliang.wyl@...baba-inc.com>
Subject: Re: Would you help to tell why async printk solution was not taken to upstream kernel ?

Hi Steve,  

On Sun, 04 Mar 2018 23:43:23 +0800
Steven Rostedt <rostedt@...dmis.org> wrote:

> Yes, people keep bringing up this scenario.
> It would require a single burst of printks to all CPUs. And then no
> more printks after that. The last one will end up printing the entire
> buffer out the slow console. The thing is, this is a bounded time, and
> no printk will print more than one full buffer worth.

> If this is a worry, then set the timeouts for the lockup detection to
> be longer than the time it takes to print one full buffer with the
> slowest console.

Thanks for your information and suggestion. We will think of backport 
the code as per the workload, or recently, maybe we will think of disable 
ttyS0 console just for the printk. 

Thanks & Regards
Qixuan