linux-kernel - Re: [PATCH] Don't map random pages if swapoff errors

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] [day] [month] [year] [list]

Message-ID: <20070119191615.GA16601@ms2.inr.ac.ru>
Date:	Fri, 19 Jan 2007 22:16:15 +0300
From:	Alexey Kuznetsov <kuznet@....inr.ac.ru>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	Alexey Dobriyan <adobriyan@...nvz.org>,
	Andrew Morton <akpm@...l.org>,
	Richard Purdie <richard@...nedhand.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Don't map random pages if swapoff errors

Hello!

> Getting an error there is all the more reason to proceed
> with the swapoff, not to give up and break out of it.

Yes, from this viewpoint more reasonable approach would be to untie
corresponding ptes from swap entry and mark them as invalid to trigger
fault on access.

Not even tried simply because it is definitely not that thing, which
we needed. We used this for process migration and for that purpose
we really need to know when swapoff() fails ASAP to abort migration,
to kill processes which got invalid pages and to resume original copy.
Obviously, delayed fault is absolutely inappropriate for this particular
purpose.

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