linux-kernel - [RFC 0/2] prctl: set-mm -- Rework interface

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

Message-Id: <20140703143318.568554771@openvz.org>
Date:	Thu, 03 Jul 2014 18:33:18 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	linux-kernel@...r.kernel.org
Cc:	gorcunov@...nvz.org
Subject: [RFC 0/2] prctl: set-mm -- Rework interface

Hi!

While been implementing c/r for user-namespaces we found that
having CAP_SYS_RESOURCE requirement in prctl set-mm opcode is somewhat
inconvenient and doesn't allow us to proceed restore of user-ns
since we loose CAP_SYS_RESOURCE upon new user-ns creation.

So it looks better to provide new interface and deprecate old one
leaving cap-sys-resource behind.

I would highly appreciate any comments on validate_prctl_map_locked()
helper in second patch which tests for new struct mm_struct values
being sane. I hope I didn't miss something obvious but as fas as
I see even using some "bad" values can't affect the kernel since
members are used mostly for statistics purpose.

Please take a look once time permit, any comments are highly
appreciated.

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