netdev - Re: [PATCH net-next 0/2] enetc: Clean endianness warnings up

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:   Wed, 25 Nov 2020 14:55:23 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Claudiu Manoil <claudiu.manoil@....com>
Cc:     netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next 0/2] enetc: Clean endianness warnings up

On Wed, 18 Nov 2020 09:54:35 -0800 Jakub Kicinski wrote:
> On Wed, 18 Nov 2020 09:52:58 -0800 Jakub Kicinski wrote:
> > On Tue, 17 Nov 2020 20:20:02 +0200 Claudiu Manoil wrote:  
> > > Cleanup patches to address the outstanding endianness issues
> > > in the driver reported by sparse.    
> > 
> > Build bot says this doesn't apply to net-next, could you double check?  
> 
> Hm, not sure what happened there, it does seem to apply now.

Ah, I figured it out now. Apparently Patchwork orders the patches by
date / its own patch ID (assigned at arrival time).

When mbox for the series is downloaded things work correctly, but build
bot tries to fetch patches one by one, and there if patches arrived at
the mailing list out of order - they don't apply.

This wasn't as evident here with just two patches seemingly in the
right order but Randy just posted a 10 patch series which has the same
issue.

I reported it upstream [1] and tried to work around it in the bot.

Fingers crossed.

[1] https://github.com/getpatchwork/patchwork/issues/386