change in protections of /proc/$pid/mem

From: Kees Cook
Date: Wed Jan 18 2012 - 15:57:14 EST


Hi,

In e268337dfe26dfc7efd422a804dbb27977a3cccc, the logic for interacting
with /dev/$pid/mem was changed. It seems that the requirement that the
reader/writer must be actively attached to the inferior has been
dropped. Is this wise, to allow multiple read/writers of /dev/$pid/mem
even if they are not ptracing? The protection has been there for a
while, and I don't see the reason for removing it. I can't find a
discussion about this change -- where did that happen?

-Kees

--
Kees Cook
ChromeOS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/