linux-kernel - Re: [PATCH v3 1/2] [DONE REQ CHG] test_firmware: prevent race conditions by a correct implementation of locking

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:   Fri, 4 Aug 2023 19:15:10 +0200
From:   Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org,
        "Luis R . Rodriguez" <mcgrof@...nel.org>,
        Russ Weight <russell.h.weight@...el.com>,
        Takashi Iwai <tiwai@...e.de>,
        Tianfei Zhang <tianfei.zhang@...el.com>,
        Shuah Khan <shuah@...nel.org>,
        Colin Ian King <colin.i.king@...il.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-kselftest@...r.kernel.org, stable@...r.kernel.org,
        Dan Carpenter <error27@...il.com>
Subject: Re: [PATCH v3 1/2] [DONE REQ CHG] test_firmware: prevent race
 conditions by a correct implementation of locking

Hi, Mr. Greg,

On 8/4/23 13:22, Greg Kroah-Hartman wrote:
> On Thu, Aug 03, 2023 at 06:53:04PM +0200, Mirsad Todorovac wrote:
>> [ Upstream commit 4acfe3dfde685a5a9eaec5555351918e2d7266a1 ]
> 
> <snip>
> 
> Ok, I am totally confused as to what patch is the newest one, and which
> is for what branches, sorry.
> 
> So, I've deleted all of the patches from my review queue and I would ask
> that you start over.
> 
> Note, if you put the kernel version in the subject line, it makes it
> simpler for me to understand what goes where.
> 
> Here is an example to follow:
> 	https://lore.kernel.org/r/20230802170227.1590187-1-eahariha@linux.microsoft.com
> 
> There are loads of other examples on the stable mailing list, please
> don't make it hard for me to understand what to do here, make it obvious
> as I'm dealing with hundreds of patches a day.

Done requested changes and resubmitted. I hope it is done right this time. Of course,
it could be better still, but this should work out.

It is a paramount that we make your life with applying patches easier and this is
a new situation that I haven't got covered yet.

I will also try to imitate the skilled patch submitters the next time before wasting
your time or reinventing the wheel.

> thanks,

You're welcome.

Kind regards,
Mirsad