linux-kernel - Re: Problems with suspend and USB storage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080515180321.GB22097@nostromo.devel.redhat.com>
Date:	Thu, 15 May 2008 14:03:21 -0400
From:	Bill Nottingham <notting@...hat.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: Problems with suspend and USB storage

Tino Keitel (tino.keitel@....de) said: 
> On Thu, May 15, 2008 at 12:33:15 -0400, Bill Nottingham wrote:
> 
> [...]
> 
> > Is there any way to get sane behavior out of suspend/resume with
> > USB storage?
> 
> I use this since 2.6.18, with my /home, one swap partition and some
> other partitions on a USB hard disk. However, I use LVM, what might be
> a good idea as the device names doesn't matter in this case (just a
> guess). I never had any such failure with suspend to disk and to RAM as
> described above.

Throwing device-mapper in the middle (for crypto) doesn't actually help
the situation.

In any case, even if device names aren't stable across boot, they sort
of need to be across suspend and resume for active filesystems...

Bill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/