Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #65146 > unrolled thread

Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2019-09-20 22:50 +0200
Last post2020-09-06 11:40 +0200
Articles 2 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled Salvatore Bonaccorso <carnil@debian.org> - 2019-09-20 22:50 +0200
    Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled Salvatore Bonaccorso <carnil@debian.org> - 2020-09-06 11:40 +0200

#65146 — Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled

FromSalvatore Bonaccorso <carnil@debian.org>
Date2019-09-20 22:50 +0200
SubjectBug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled
Message-ID<yIy0N-7QW-1@gated-at.bofh.it>
Hi Simon,

On Mon, May 06, 2019 at 10:28:09PM +0200, Simon Richter wrote:
> Hi,
> 
> On 06.05.19 21:35, Simon Richter wrote:
> 
> > I can probably test intermediate versions and/or changes in setup, but this
> > is difficult to automate because "bad" runs require manual file system
> > repairs and every run requires LUKS setup to be repeated.
> 
> FWIW, using a separate LV and swapon --discard=pages seems to work, so
> this is likely to be specific to swap files (which normally shouldn't be
> affected by discards, as their allocation doesn't change, but the kernel
> might have some default behaviour here that I'm not aware of).

Possible for you to directly report that upstream, keeping the bug in
the loop? (is it still an issue with 5.2.x and 5.3)?

Regards,
Salvatore

[toc] | [next] | [standalone]


#68008

FromSalvatore Bonaccorso <carnil@debian.org>
Date2020-09-06 11:40 +0200
Message-ID<ALZjs-7o9-9@gated-at.bofh.it>
In reply to#65146
Hi Simon,

On Fri, Sep 20, 2019 at 10:42:17PM +0200, Salvatore Bonaccorso wrote:
> Hi Simon,
> 
> On Mon, May 06, 2019 at 10:28:09PM +0200, Simon Richter wrote:
> > Hi,
> > 
> > On 06.05.19 21:35, Simon Richter wrote:
> > 
> > > I can probably test intermediate versions and/or changes in setup, but this
> > > is difficult to automate because "bad" runs require manual file system
> > > repairs and every run requires LUKS setup to be repeated.
> > 
> > FWIW, using a separate LV and swapon --discard=pages seems to work, so
> > this is likely to be specific to swap files (which normally shouldn't be
> > affected by discards, as their allocation doesn't change, but the kernel
> > might have some default behaviour here that I'm not aware of).
> 
> Possible for you to directly report that upstream, keeping the bug in
> the loop? (is it still an issue with 5.2.x and 5.3)?

Did you had a chance to check this?

Regards,
Salvatore

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web