[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150116110013.GA29182@node.dhcp.inet.fi>
Date: Fri, 16 Jan 2015 13:00:13 +0200
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Rasmus Villemoes <linux@...musvillemoes.dk>,
Calvin Owens <calvinowens@...com>,
Siddhesh Poyarekar <siddhesh.poyarekar@...il.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>,
linux-kernel <linux-kernel@...r.kernel.org>, kernel-team@...com
Subject: Re: [RFC][PATCH] procfs: Add /proc/<pid>/mapped_files
On Thu, Jan 15, 2015 at 05:15:43PM -0800, Andrew Morton wrote:
> On Thu, 15 Jan 2015 00:51:50 +0100 Rasmus Villemoes <linux@...musvillemoes.dk> wrote:
>
> > > There are still several flags unused in vma.vm_flags btw.
> > >
> > > I'm not sure that we can repurpose vm_pgoff (or vm_private_data) for
> > > this: a badly behaved thread could make its sp point at a random vma
> > > then trick the kernel into scribbling on that vma's vm_proff?
> >
> > Well, we could still check vm_file for being NULL before writing to
> > vm_pgoff/vm_stack_tid.
>
> Yes, I guess that would work. We'd need to check that nobody else
> is already playing similar games with vm_pgoff.
Well, we do use ->vm_pgoff in anonymous VMAs. For rmap in particular --
vma_address().
--
Kirill A. Shutemov
--
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