linux-kernel - Re: [PATCH[RFC] kill sysrq-u (emergency remount r/o)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.61.0702052136310.19384@yvahk01.tjqt.qr>
Date:	Mon, 5 Feb 2007 21:40:08 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Christoph Hellwig <hch@....de>
cc:	akpm@...l.org, haveblue@...ibm.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH[RFC] kill sysrq-u (emergency remount r/o)


On Feb 5 2007 18:32, Christoph Hellwig wrote:
>
>in two recent discussions (file_list_lock scalability and remount r/o
>on suspend) I stumbled over this emergency remount feature.  It's not
>actually useful because it tries a potentially dangerous remount
>despite writers still beeing in progress, which we can't get rid.

The current way is to remount things, and return -EROFS to any process
that attempts to write(). Unless we want to kill processes to get rid of
them [most likely we possibly won't], I am fine with how things are atm.
So, what's the "dangerous" part, actually?

>Any ideas and comments?

sysrq+u is helpful. It is like \( sysrq+s && make sure no further writes
go to disk \).



Jan
-- 
-
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/