On Sat, 2022-10-29 at 09:23 +0200, Salvatore Bonaccorso wrote:
>
> No unfortunately we cannot do that. The reason is similar to what
> lead
> to
> https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
> or caused bugs like #916927.
Forgive me my ignorance,
On 2022-10-29 09:23, Salvatore Bonaccorso wrote:
So question is,.. would it make sense to request that linux-image-amd64
depends on the signed | unsigned version?
No unfortunately we cannot do that. The reason is similar to what lead
to
Hi Christoph,
On Sat, Oct 29, 2022 at 12:36:01AM +0200, Christoph Anton Mitterer wrote:
> Hey Salvatore.
>
> On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> > I did decide to still do so, so we can have the CVE fix migrate
> > finally to testing (which took some time as well
Hey Salvatore.
On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> I did decide to still do so, so we can have the CVE fix migrate
> finally to testing (which took some time as well given there was the
> perl transition ongoing).
Fine for me... I think it would be nice if there was
Control: severity -1 serious
Hi Christoph,
Thanks for the quick feedback!
On Thu, Oct 27, 2022 at 09:10:53PM +0200, Christoph Anton Mitterer wrote:
> Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso
> :
> >According to your references there is the workaround of mounting with
>
Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso
:
>According to your references there is the workaround of mounting with
>clear_cache,space_cache=v2 and convert the filesystem.
>
>What would one prevent doing so?
v2 space cache is still rather new and had only recently some
Control: severity -1 important
Hi,
On Wed, Oct 26, 2022 at 10:23:35PM +0200, Christoph Anton Mitterer wrote:
> Source: linux
> Version: 5.19.6-1
> Severity: critical
> Justification: breaks the whole system
>
>
> Hi.
>
> 6.0.3 introduced a commit that causes (permanent) CPU soft lockups
> for
Control: retitle -1 6.0.5 fixes critical btrfs bug in 6.0.3, affecting space
cache v1 filesystems
Control: notfound -1 5.19.6-1
Control: found -1 6.0.3-1
No idea why reportbug picked 5.19.6, which I have not even installed
anymore... o.O
Source: linux
Version: 5.19.6-1
Severity: critical
Justification: breaks the whole system
Hi.
6.0.3 introduced a commit that causes (permanent) CPU soft lockups
for some people with btrfs filesystems, effectively breaking the
system, e.g. when booting.
See e.g.
9 matches
Mail list logo
