linux-kernel - Re: [PATCH V7 2/4] softirq: Factor loop termination condition

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]

Date:   Thu, 24 Sep 2020 14:31:27 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     qianjun.kernel@...il.com, peterz@...radead.org, will@...nel.org,
        luto@...nel.org, linux-kernel@...r.kernel.org
Cc:     laoar.shao@...il.com, qais.yousef@....com, urezki@...il.com,
        jun qian <qianjun.kernel@...il.com>
Subject: Re: [PATCH V7 2/4] softirq: Factor loop termination condition

On Thu, Sep 24 2020 at 10:36, Thomas Gleixner wrote:

> On Tue, Sep 15 2020 at 19:56, qianjun kernel wrote:
>>  asmlinkage __visible void __softirq_entry __do_softirq(void)
>>  {
>>  	u64 start = sched_clock();
>>  	unsigned long old_flags = current->flags;
>> -	int max_restart = MAX_SOFTIRQ_RESTART;
>> +	unsigned int max_restart = MAX_SOFTIRQ_RESTART;
>
> And this change is related to making the timeout check a function in
> which way?

Aside of that looking at:

      https://lore.kernel.org/r/20200911155555.GX2674@hirez.programming.kicks-ass.net

Peter gave you a series of patches, granted they are untested and
lacking proper changelogs. But you go and repost them mostly unmodified
and taking authorship of them.

This not the way it works. You cannot claim authorship of something you
did not write yourself. See Documentation/process/ for detailed
explanation how to handle patches which you got from someone else.

Thanks,

        tglx