Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled
- To: Simon Richter <sjr@debian.org>
- Cc: 928526@bugs.debian.org
- Subject: Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sun, 6 Sep 2020 11:32:47 +0200
- Message-id: <[🔎] 20200906093247.GA707107@eldamar.local>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 928526@bugs.debian.org
- In-reply-to: <20190920204217.GA32602@eldamar.local>
- References: <155717132576.2953.18378172143087240730.reportbug@coffee> <155717132576.2953.18378172143087240730.reportbug@coffee> <32ec4180-a408-235a-4648-25b6cab61e55@debian.org> <155717132576.2953.18378172143087240730.reportbug@coffee> <20190920204217.GA32602@eldamar.local> <155717132576.2953.18378172143087240730.reportbug@coffee>
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
Reply to: