HI

I urge you to pay close attention to this incident once again. thanks Please don't let the Linux kernel community be filled with robbers and thieves!

On April 12th, 2024, at 00:57, I sent the vulnerability and explained the situation to the maintainer at rafael@kernel.org and viresh.kumar@linaro.org. At 02:11 on April 12th, 2024, Rafael replied to me, asking me to submit it to the main branch. At 07:18 on April 12th, 2024, I submitted the vulnerability to the main branch. At 11:24 on April 12th, 2024, Viresh Kumar replied to me, confirming that the vulnerability was legitimate. At 13:49 on April 12th, 2024, Viresh Kumar released the patch to the main list. Here is the patchs I submitted to the main line .

cpufreq: Remove redundant exit() functions https://lore.kernel.org/all/20240409141909.4413-1-sensor1010@163.com/

cpufreq: Convert to exit callback returning void https://lore.kernel.org/all/20240410132247.3587-1-sensor1010@163.com/

cpufreq: Covert to offline callback returning void https://lore.kernel.org/all/20240411150620.19262-1-sensor1010@163.com/

cpufreq: Fixed kernel crash caused by cpufreq issues https://lore.kernel.org/all/20240411231818.2471-1-sensor1010@163.com/

Viresh Kumar, are you not a robber and thief? As a maintainer, do you really not care about the healthy development of the community and only defend your own interests?

It was me who first released the patch and publicly disclosed the vulnerability to the main branch. Viresh Kumar only understood the principle of the vulnerability after seeing my submitted patch. Moreover, I communicated with you later and requested to add my signature to the patch, but you refused to communicate. Your behavior fully demonstrates that you are a selfish person.

I don't understand why there can be such a selfish person in a country where Buddhism was born, and this person is even a maintainer!

At 2024-04-12 22:41:27, "lizhe" sensor1010@163.com wrote:

Let's both take a step back and add my signature to the patch, since I was the one who discovered and reported the vulnerability.

HI

i will review how it all started. 1. i reported the vulnerability to the maintainer.

2. manitaner replay me

3. i report to main line

4. you reply me

5 . you report to main line

You submitted the patch to the mainline after you learned about the vulnerability from the patch I submitted

At 2024-04-12 21:54:00, "lizhe" sensor1010@163.com wrote:

Hi

Viresh Kumar please add my name to the signature. because i discovered this vulnerability. please reply me. thanks

At 2024-04-12 18:28:56, "Greg KH" gregkh@linuxfoundation.org wrote:

On Fri, Apr 12, 2024 at 02:51:08PM +0530, Viresh Kumar wrote:

...

On 12-04-24, 17:05, lizhe wrote:

...

I found it first and submitted it to the main line first. Please be fair and just. Let him withdraw his patch.

Well, I decided not to reply to your emails anymore but this needs to be clarified a bit now.

You sent a lot of patches, over and over again and it was a mess. I saw the this [1] series first and went over to read the code and fixed an issue which I found (by the $subject patch).

Later I read your other patch [2], which I Acked roughly two hours back and yes you did send a patch that fixed the problem partially. I never saw it earlier, which is okay and it happens. Despite me giving an Ack to your patch, you have sent half-a-dozen more emails..

Then I posted a newer version of my patch some time back, removing the bits you already fixed [3].

That is all one side of the story. But all the noise you have created here has really demotivated people to review your stuff now.

-- Viresh

[1] https://lore.kernel.org/all/20240410132132.3526-1-sensor1010@163.com/ [2] https://lore.kernel.org/all/20240411231818.2471-1-sensor1010@163.com/ [3] https://lore.kernel.org/all/68294ce534668c6ab3b71a1b3e6650227c6e1f20.1712911...

Thanks for the links, I don't see that you did anything wrong here at all.

Lizhe, you seem to be confused as to how kernel development works. I suggest you take some time off and read up on how this all is supposed to happen and then work with some local people, in person, to get this figured out first, before submitting changes again.

thanks,

greg k-h