linux-kernel - Re: [PATCH 4/6] scftorture: always log error message

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]

Message-ID: <15e9b661-d61b-f555-b16e-671a4aabc8db@intel.com>
Date:   Wed, 3 Nov 2021 16:24:53 +0800
From:   Li Zhijian <zhijianx.li@...el.com>
To:     paulmck@...nel.org
Cc:     dave@...olabs.net, joel@...lfernandes.org, josh@...htriplett.org,
        mathieu.desnoyers@...icios.com, rostedt@...dmis.org,
        rcu@...r.kernel.org, philip.li@...el.com, lizhijian@...fujitsu.com,
        jiangshanlai@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/6] scftorture: always log error message



On 03/11/2021 00:06, Paul E. McKenney wrote:
> On Fri, Oct 29, 2021 at 05:40:27PM +0800, Li Zhijian wrote:
>> Generally, error message should be logged anyhow.
>>
>> Signed-off-by: Li Zhijian<zhijianx.li@...el.com>
> I have queued the patches up to this point for the v5.17 merge window
> (not the current one, but the next one).
>
> This one does not apply.  It looks like you created it against mainline
> rather than -rcu.  You can learn about the -rcu tree and its habits here:
>
> https://mirrors.edge.kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html
>
> Please port this patch to -rcu so that I can pull it in without
> conflicting with patches in -rcu.
Glad to know this, i will rebase the rest 2 patches and resubmit them soon.

Thanks
Zhijian


>