From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/3] ARM: vfp: Use vfp_lock() in vfp_entry().
Date: Tue, 27 Jun 2023 14:32:39 +0100 [thread overview]
Message-ID: <ZJrk90JUNXuF+cX4@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAMj1kXE08CMsVj=sLME4qToy1gczo9XEzTk67kaBGjyfXaf63g@mail.gmail.com>
On Tue, Jun 27, 2023 at 03:26:16PM +0200, Ard Biesheuvel wrote:
> On Tue, 27 Jun 2023 at 15:22, Russell King (Oracle)
> <linux@armlinux.org.uk> wrote:
> > as the patch system is down for the long term until Debian
> > fix their mariadb security regression which prevents a server requiring
> > a minimum of TLS v1.2 accepting connections from Debian Bookworm
> > systems (which regress from supporting TLS v1.3 to a maximum of TLS
> > v1.1).
> >
> > I reported this as a bug to the debian BTS last week, and as I have
> > come to expect from useless waste of space distro bug tracking systems,
> > there has been zero reaction - and as the bug has already been reported
> > by others, and they've been fobbed off by the package maintainer, I am
> > not hopeful that this regression will ever be fixed.
> >
> > It seems to me that Debian is ripe for having a CVE raised against
> > Bookworm for the regression, especially as TLS v1.1 is now regarded
> > as vulnerable due to downgrade attacks - and maybe that will make
> > Debian sit up and take notice.
> >
>
> Does this mean the ARM tree is closed for business a the moment? Is
> there no way to carry on without the patch system?
Only if you want to see just how utterly terrible I am trying to pick
patches off the mailing list...
IMHO, the better thing would be to apply pressure to Debian to get
them to at least recognise their cockup, so that then we have some
idea when stuff can be resurected.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-27 13:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 10:16 [PATCH 0/3] ARM: vfp: Introduce vfp_lock() for VFP locking Sebastian Andrzej Siewior
2023-06-15 10:16 ` [PATCH 1/3] ARM: vfp: Provide " Sebastian Andrzej Siewior
2023-06-15 10:16 ` [PATCH 2/3] ARM: vfp: Use vfp_lock() in vfp_sync_hwstate() Sebastian Andrzej Siewior
2023-06-15 10:16 ` [PATCH 3/3] ARM: vfp: Use vfp_lock() in vfp_entry() Sebastian Andrzej Siewior
2023-06-27 10:22 ` Ard Biesheuvel
2023-06-27 12:41 ` Sebastian Andrzej Siewior
2023-06-27 12:57 ` Ard Biesheuvel
2023-06-27 13:06 ` Sebastian Andrzej Siewior
2023-06-27 13:22 ` Russell King (Oracle)
2023-06-27 13:26 ` Ard Biesheuvel
2023-06-27 13:32 ` Russell King (Oracle) [this message]
2023-06-27 14:40 ` Russell King (Oracle)
2023-06-27 15:02 ` Russell King (Oracle)
2023-06-27 17:41 ` Russell King (Oracle)
2023-07-28 16:19 ` Sebastian Andrzej Siewior
2023-06-27 13:34 ` Sebastian Andrzej Siewior
2023-09-07 13:53 ` [PATCH 0/3] ARM: vfp: Introduce vfp_lock() for VFP locking Ard Biesheuvel
2023-09-26 11:03 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZJrk90JUNXuF+cX4@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).