linux-kernel - Re: [patch 1/1] PM: Adds remount fs ro at suspend

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: <20070206143231.GD18392@khazad-dum.debian.net>
Date:	Tue, 6 Feb 2007 12:32:31 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Nigel Cunningham <nigel@...el.suspend2.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, akuster@...sta.com,
	linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [patch 1/1] PM: Adds remount fs ro at suspend

On Tue, 06 Feb 2007, Nigel Cunningham wrote:
> Why do you think remounting filesystems is necessary? Are you getting
> problems with some particular filesystem?

No.  But anything in a removable device neets to be either remounted
read-only or unmounted if that is at all possible, because the user could
unplug it.  It is of course, sync'd anyway, so if the remount/umount fails,
no corruption should happen...  but the fs will be dirty, etc.

It can get very ugly when you factor in docks and removable bays. It's not
just USB/firewire mass-storage devices and memory cards.  And there is the
patological cases where the user suspends with the device in one port, and
resumes with the device in another port.

I feel userspace *can* do all that needs to be done, but we are (currently)
very bad at it.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
-
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/