linux-kernel - Re: [PATCH v2] loongarch/mm: disable WUC for pgprot_writecombine as same as ioremap

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: <3e493e1e-07cb-40ff-823b-d166d0261a2a@kernel.org>
Date: Fri, 20 Dec 2024 09:43:34 -0700
From: Shuah <shuah@...nel.org>
To: Sui Jingfeng <sui.jingfeng@...ux.dev>, Shuah <shuah@...nel.org>,
 Xi Ruoyao <xry111@...111.site>, WANG Xuerui <kernel@...0n.name>,
 Icenowy Zheng <uwu@...nowy.me>, Huacai Chen <chenhuacai@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
 "Mike Rapoport (IBM)" <rppt@...nel.org>, Baoquan He <bhe@...hat.com>,
 "Matthew Wilcox (Oracle)" <willy@...radead.org>,
 David Hildenbrand <david@...hat.com>, Zhen Lei <thunder.leizhen@...wei.com>,
 Thomas Gleixner <tglx@...utronix.de>, Zhihong Dong <donmor3000@...mail.com>,
 loongarch@...ts.linux.dev, linux-kernel@...r.kernel.org,
 "conduct@...nel.org" <conduct@...nel.org>
Subject: Re: [PATCH v2] loongarch/mm: disable WUC for pgprot_writecombine as
 same as ioremap_wc

On 12/17/24 20:24, Sui Jingfeng wrote:
> Hi,
> 
> 
> On 2024/12/18 02:18, Shuah wrote:
>> On 12/2/24 09:23, Sui Jingfeng wrote:
>>> Hi,
>>>
>>
>>>> IIUC this is a hardware bug of 7A1000 and 7A2000, so the proper location
>>>> of the workaround is in the bridge chip driver.  Or am I
>>>> misunderstanding something?
>>>>
>>>
>>> You are misunderstanding everything and ranting like a dog.
>>>
>>
>> Sui Jingfeng,
>>
>> This is not the way to work with your fellow developers in the
>> community to express disagreements.
> 
> 
> I'm not expressing disagreements, but argue that the contributor
> and/or talker should provide *sufficient* hardware details and
> tests. Instead of pointless *ranting* in order to get harmful
> patch merged.
> 
> The discussion completely not make scene at all.
> 
> 
>> I would recommend following up with an apology.
>>
> 
> I will not apology to indecent contributors and/or maintainers
> like this, never.
> 

Either way the way the wording you are using your discussion is
not what is expected and understood as the code of conduct.

https://docs.kernel.org/process/code-of-conduct.html

thanks,
-- Shuah (On behalf of the Code of Conduct Committee)