All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: stable <stable@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Subject: Regressions in stable releases
Date: Thu, 5 Aug 2021 09:11:02 -0700	[thread overview]
Message-ID: <efee3a58-a4d2-af22-0931-e81b877ab539@roeck-us.net> (raw)

Hi folks,

we have (at least) two severe regressions in stable releases right now.

[SHAs are from linux-5.10.y]

2435dcfd16ac spi: mediatek: fix fifo rx mode
	Breaks SPI access on all Mediatek devices for small transactions
	(including all Mediatek based Chromebooks since they use small SPI
	 transactions for EC communication)

60789afc02f5 Bluetooth: Shutdown controller after workqueues are flushed or cancelled
	Breaks Bluetooth on various devices (Mediatek and possibly others)
	Discussion: https://lkml.org/lkml/2021/7/28/569

Unfortunately, it appears that all our testing doesn't cover SPI and Bluetooth.

I understand that upstream is just as broken until fixes are applied there.
Still, it shows that our test coverage is far from where it needs to be,
and/or that we may be too aggressive with backporting patches to stable
releases.

If you have an idea how to improve the situation, please let me know.

Thanks,
Guenter

             reply	other threads:[~2021-08-05 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 16:11 Guenter Roeck [this message]
2021-08-05 16:19 ` Regressions in stable releases Greg Kroah-Hartman
2021-08-05 17:39   ` Guenter Roeck
2021-08-05 17:43     ` Greg Kroah-Hartman
2021-08-05 19:44       ` Guenter Roeck
2021-08-05 19:51         ` Greg Kroah-Hartman
2021-08-05 16:42 ` Willy Tarreau
2021-08-05 17:29   ` Guenter Roeck
2021-08-05 18:30     ` Willy Tarreau
2021-08-06 14:16       ` Guenter Roeck
2021-08-06 14:42         ` Willy Tarreau
2021-08-06 14:37       ` Sasha Levin
2021-08-06 14:52         ` Willy Tarreau

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=efee3a58-a4d2-af22-0931-e81b877ab539@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.