linux-kernel - Re: [PATCH] staging: pi433: prevent uninitialized data from being printed out

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:   Mon, 28 Feb 2022 09:44:15 +0300
From:   Dan Carpenter <dan.carpenter@...cle.com>
To:     Pavel Skripkin <paskripkin@...il.com>
Cc:     Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@...il.com>,
        gregkh@...uxfoundation.org, realwakka@...il.com,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: pi433: prevent uninitialized data from being
 printed out

On Sat, Feb 26, 2022 at 04:08:48PM +0300, Pavel Skripkin wrote:
> > Patch dependency:
> > 
> > - this patch depends on the following patch to be applied first as
> > both of them change the same file:
> > https://lore.kernel.org/lkml/Yhla4a1Clpguoo2h@mail.google.com/
> > ---
> 
> You can send all these patches as a patch series with proper order. It will
> help maintainers to not break the order while applying.
> 

1) All what Pavel said is true.
2) In this case the order does not matter so this text is confusing and
   unnecessary.
3) Greg is going to see that and he is *never* going to click on that
   link.  In staging then we do not care about the order of patches.
   Everything is applied in first come first serve basis.  If Greg finds
   out that order matters and it is not sent as a patch set then he
   just deletes all your patches and asks you to resend everything
   correctly.

regards,
dan carpenter