linux-kernel - Re: Linux regressions report for mainline [2022-07-24]

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: <CAHk-=wjZ8snqJmoyhHjZCYVP5bMmNWzQMkDZ6LtNr1YKEg4A9w@mail.gmail.com>
Date:   Sun, 24 Jul 2022 12:58:56 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Regzbot (on behalf of Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: Linux regressions report for mainline [2022-07-24]

On Sun, Jul 24, 2022 at 12:48 PM Regzbot (on behalf of Thorsten
Leemhuis) <regressions@...mhuis.info> wrote:
>
> * The following patch fixing a build bug reported three times now, that
> didn't get any reaction from the maintainer since it was posted six days
> ago:
> https://lore.kernel.org/lkml/20220717231105.33005-1-kilobyte@angband.pl/

Ok. DavidH is on vacation, so I just picked that up directly.

> * The virtio regression is kinda fixed by c346dae4f3fb already, but
> there is a patch in the branch Michael usually uses to sent patches to
> you that he for one reason or another hasn't sent your way yet:
> https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h=vhost&idj9720576cd00d30722c5f755bd17d4cfa9df636
> I asked what's up here a few days ago, but sadly got no reply.

I'll let this be for now. It's more of a "don't do that then" thing,

> [ *NEW* ] fs: recent changes to copy_file_range behavior breakage

This seems to be a "damned if you do, damned if you don't", in that
different versions of libtorrent seem to expect different behaviors.

I think we're leaving it be, so that there's just one behavior going
forward, rather than vacillate between two and making things just
worse and oscillate depending on which one people use.

Not good, but there doesn't seem to be a good case.

               Linus