[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150126225023.df63f6ca.akpm@linux-foundation.org>
Date: Mon, 26 Jan 2015 22:50:23 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Cyrill Gorcunov <gorcunov@...il.com>
Cc: "Kirill A. Shutemov" <kirill@...temov.name>,
Calvin Owens <calvinowens@...com>,
Alexey Dobriyan <adobriyan@...il.com>,
Oleg Nesterov <oleg@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Al Viro <viro@...iv.linux.org.uk>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Peter Feiner <pfeiner@...gle.com>,
Grant Likely <grant.likely@...retlab.ca>,
Siddhesh Poyarekar <siddhesh.poyarekar@...il.com>,
linux-kernel@...r.kernel.org, kernel-team@...com,
Pavel Emelyanov <xemul@...nvz.org>, linux-api@...r.kernel.org,
Kees Cook <keescook@...omium.org>
Subject: Re: [RFC][PATCH v2] procfs: Always expose /proc/<pid>/map_files/
and make it readable
On Tue, 27 Jan 2015 09:46:47 +0300 Cyrill Gorcunov <gorcunov@...il.com> wrote:
> > There's one other problem here: we're assuming that the map_files
> > implementation doesn't have bugs. If it does have bugs then relaxing
> > permissions like this will create new vulnerabilities. And the
> > map_files implementation is surprisingly complex. Is it bug-free?
>
> I didn't find any bugs in map-files (and we use it for long time already)
> so I think it is safe.
You've been using map_files the way it was supposed to be used so no,
any bugs won't show up. What happens if you don your evil black hat
and use map_files in ways that weren't anticipated? Attack it?
--
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/
Powered by blists - more mailing lists