linux-kernel - Re: [RESEND PATCH] time: changed timespec64_to

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 11 Sep 2021 02:48:21 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     OPENSOURCE Lukas Hannen 
        <lukas.hannen@...nsource.tttech-industrial.com>,
        John Stultz <john.stultz@...aro.org>,
        "EMC: linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH] time: changed timespec64_to_ns to avoid underrun

Lukas,

On Fri, Sep 10 2021 at 13:50, OPENSOURCE Lukas Hannen wrote:

> This patch fixes a small oversight in timespec64_to_ns() that has resulted
...

why you are resending this patch?

1) The only change you did is adding a prefix to the subject line

   which in fact disqualifies it from the RESEND tag because RESEND
   means it's unmodified or just forward ported.

   Changed patches even if the change is just in the subject line or the
   changelog want a version number.

   But what's worse:

2) You ignored any other review comment I gave here:

   https://lore.kernel.org/r/87y2876pg0.ffs@tglx

   IOW, you stopped reading at line 12 of my reply

3) Due to that you failed to notice that I said in that reply:

   "I fixed it up for you this time."

4) Of course you also ignored the fact that I actually fixed the
   identified issues and the fact that the fixed up patch is already
   applied to my tree.

   You got notfied about that:

   https://lore.kernel.org/r/163111620295.25758.18154572095175068828.tip-bot2@tip-bot2

So what exactly are you trying to achieve by "resending" a patch which
still does not apply and still has a non-sensical subject line and
changelog?

> CONFIDENTIALITY: The contents of this e-mail are confidential and
> intended only for the above addressee(s). If you are not the intended
> recipient, or the person responsible for delivering it to the intended
> recipient, copying or delivering it to anyone else or using it in any
> unauthorized manner is prohibited and may be unlawful. If you receive
> this e-mail by mistake, please notify the sender and the systems
> administrator at straymail@...ech.com immediately.

Please get rid of this nonsensical disclaimer.

 When posting to public mailing lists the boilerplate confidentiality
 disclaimers are not only meaningless, they are absolutely wrong for
 obvious reasons.

 See https://people.kernel.org/tglx/notes-about-netiquette for further
 information.

Thanks,

        tglx