linux-kernel - Re: linux-next: Tree for Oct 25

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] [day] [month] [year] [list]

Date:   Thu, 28 Oct 2021 20:54:40 +0800
From:   Xianting Tian <xianting.tian@...ux.alibaba.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Shile Zhang <shile.zhang@...ux.alibaba.com>
Subject: Re: linux-next: Tree for Oct 25


在 2021/10/28 下午8:48, Stephen Rothwell 写道:
> Hi Xianting,
>
> On Thu, 28 Oct 2021 15:59:02 +0800 Xianting Tian <xianting.tian@...ux.alibaba.com> wrote:
>> 在 2021/10/28 下午12:51, Stephen Rothwell 写道:
>>> Hi Xianting,
>>>
>>> On Thu, 28 Oct 2021 09:51:00 +0800 Xianting Tian <xianting.tian@...ux.alibaba.com> wrote:
>>>> 在 2021/10/27 下午7:42, Stephen Rothwell 写道:
>>>>> Hi all,
>>>>>
>>>>> On Mon, 25 Oct 2021 20:49:21 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>>>>> There seems to be something amiss with cnosole output in today's release
>>>>>> (at least on my ppc qemu boot tests).
>>>>> The console output seems to be back today.  I assume its repair had
>>>>> something to do with commit
>>>>>
>>>>>      60f41e848492 ("Revert "tty: hvc: pass DMA capable memory to put_chars()"")
>>>>>    >> hi Stephen，
>>>> Thanks for the info, Could you share more details about the issue you met? is it about early console print issue?
>>>>   
>>> Here is the diff between my boot logs:
>> thanks, I checked the log, Can I understand it as you missed some early bootup log  when use new release?
> yes, the console messages stopped for a while when we switched from the
> bootconsole to the final hvc0 console.
thanks, it makes sense, this commit broken the early console mechanism, 
I will submit the fix patch for reviewing soon.
>
>>> @@ -124,81 +124,9 @@
>>>     clocksource: timebase mult[1f40000] shift[24] registered
>>>     Console: colour dummy device 80x25
>>>     printk: console [hvc0] enabled
>>> - printk: console [hvc0] enabled
>>> - printk: bootconsole [udbg0] disabled
>>>     printk: bootconsole [udbg0] disabled
>>> - pid_max: default: 32768 minimum: 301
>>> - Mount-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
>>> - Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes, linear)
> 	.
> 	.
> 	.