Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1092493
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#990279: Status? |
| Date | 2022-02-08 22:30 +0100 |
| Message-ID | <DOGdH-tTL-1@gated-at.bofh.it> (permalink) |
| References | <Ctxhf-3p8-1@gated-at.bofh.it> <DOEvf-sEL-13@gated-at.bofh.it> <Ctxhf-3p8-1@gated-at.bofh.it> <DOEvf-sEL-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi Timothy, On Tue, Feb 08, 2022 at 01:23:10PM -0600, Timothy Pearson wrote: > I can confirm Bullseye is still affected by this bug. > > Is there any chance of this fix being applied to the Bullseye stable > kernels? We're having to maintain kernel builds in our own > repositories to fix this regression, and that introduces some lag > when e.g. security updates are pushed to Debian. This needs someone to submit a (tested) backport patch to stable maintainers, so it can be applied in the 5.10.y stable series. Christian, would it be possible to do that? Cf. https://bugs.debian.org/990279#42 and https://bugs.debian.org/990279#52 Regards, Salvatore
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#990279: Status? Timothy Pearson <tpearson@raptorengineering.com> - 2022-02-08 20:40 +0100
Bug#990279: Status? Timothy Pearson <tpearson@raptorengineering.com> - 2022-02-08 22:30 +0100
Bug#990279: Status? Timothy Pearson <tpearson@raptorengineering.com> - 2022-02-09 20:30 +0100
Bug#990279: Status? Salvatore Bonaccorso <carnil@debian.org> - 2022-02-09 21:30 +0100
Bug#990279: Status? Timothy Pearson <tpearson@raptorengineering.com> - 2022-02-09 21:30 +0100
Bug#990279: Status? Salvatore Bonaccorso <carnil@debian.org> - 2022-02-08 22:30 +0100
csiph-web