linux-kernel - Re: linux-next: Tree for Jul 12 (no Rust)

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]

Message-ID: <CANiq72kHCwbBU5cebPaj32dOb9DspB_fLhw3tALcw2ssxjkCdA@mail.gmail.com>
Date:   Tue, 13 Jul 2021 22:31:10 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     Stephen Rothwell <sfr@...hwell.id.au>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Miguel Ojeda <ojeda@...nel.org>
Subject: Re: linux-next: Tree for Jul 12 (no Rust)

On Tue, Jul 13, 2021 at 10:20 PM Randy Dunlap <rdunlap@...radead.org> wrote:
>
> It was either a script bug (but I haven't seen this one before)
> or a user error (more likely).
> My daily linux-next builds are started by a cron job but the don't
> always start when they should (IMO), so I may have started it
> manually... but then the error that I saw would have only happened
> if 2 linux-next builds were started at almost the same time (one
> by cron, one manually by me) - I don't know if that happened or not.
>
> Today's linux-next builds didn't have any similar problem and I doubt
> that I can reconstruct what happened exactly.

I see -- it should be unlikely that someone else sees it then.

Thanks!

Cheers,
Miguel