linux-kernel - Re: [PATCHSET v4] Add io_uring futex/futexv support

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]

Message-ID: <bda49491-4d7f-485f-b929-87a4bec6efaa@kernel.dk>
Date:   Mon, 14 Aug 2023 18:18:31 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Thomas Gleixner <tglx@...utronix.de>, io-uring@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     peterz@...radead.org, andres@...razel.de
Subject: Re: [PATCHSET v4] Add io_uring futex/futexv support

On 8/14/23 6:12 PM, Thomas Gleixner wrote:
> Jens!
> 
> On Mon, Aug 07 2023 at 12:23, Jens Axboe wrote:
>> On 8/6/23 7:23?PM, Thomas Gleixner wrote:
>>> Go and look at the amount of fallout this has caused in the last years.
>>> io-urine is definitely the leader of the pack in my security@...nel.org
>>> inbox.
>>
>> We're now resorting to name calling? Sorry, but I think that's pretty
>> low and not very professional.
> 
> I'm not resorting to that. If you got offended by the meme which
> happened to elapse into my reply, then I can definitely understand
> that. That was not my intention at all. But you might think about why
> that meme exists in the first place.

It's been there since day 1 because a) the spelling is close, and b)
some people are just childish. Same reason kids in the 3rd grade come up
with nicknames for each others. And that's fine, but most people grow
out of that, and it certainly has no place in what is supposedly a
professional setting.

>>> Vs. the problem at hand. I've failed to catch a major issue with futex
>>> patches in the past and I'm not seeing any reason to rush any of this to
>>> repeat the experience just because.
>>
>> I'm not asking anyone to rush anything.
> 
>  "As we're getting ever closer to the merge window, and I have other
>   things sitting on top of the futex series, that's problematic for me."
> 
> That's your words and how should I pretty please interpret them
> correctly?

Do I need to reorder them? And clearly looks like the answer is yes,
which is fine.

-- 
Jens Axboe