linux-kernel - Re: [PATCH 2/2 v2] core dump: add VM_NODUMP, MADV_NODUMP, MADV_CLEAR

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: <20120308214417.328502C0C8@topped-with-meat.com>
Date:	Thu,  8 Mar 2012 13:44:17 -0800 (PST)
From:	Roland McGrath <roland@...k.frob.com>
To:	Jason Baron <jbaron@...hat.com>
Cc:	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	avi@...hat.com, cmetcalf@...era.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2 v2] core dump: add VM_NODUMP, MADV_NODUMP, MADV_CLEAR_NODUMP

I'm vaguely dubious about the desireability of using this new feature.
(I would hate to try to debug a qemu bug from a dump where half the
interesting state was intentionally hidden from me.)  But I don't see
any problem with the implementation.

As to the interface, I think the bits are OK but it would be more
in keeping with the existing MADV_* names to call the new values
MADV_DONTDUMP and MADV_DODUMP.

Thanks,
Roland
--
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/