linux-kernel - Re: vvar, gup && coredump

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: <CALCETrVgrEXdCV5571WsWVHLCNvLxTLx=t5iRWY+We1dtu1e9w@mail.gmail.com>
Date:	Thu, 12 Mar 2015 11:33:31 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: vvar, gup && coredump

[removed people who will be bored]

On Thu, Mar 12, 2015 at 11:08 AM, Oleg Nesterov <oleg@...hat.com> wrote:
> On 03/12, Andy Lutomirski wrote:
>>
>> On Thu, Mar 12, 2015 at 10:39 AM, Oleg Nesterov <oleg@...hat.com> wrote:
>> > Well. Speaking of vdso. I understand that unlikely we can do this, but
>> > for uprobes it would be nice to have a anon-inode file behind this mapping,
>> > so that vma_interval_tree_foreach() could work, etc. OK, this is completely
>> > off-topic, please forget.
>>
>> Couldn't you do that directly in the uprobes code?  That is, create an
>> anon_inode file and just map it the old-fashioned way?
>
> This won't help. Uprobes wants this file mmaped by all applications, so
> that build_map_info() can find mm's, vma's, etc to install the system-wide
> breakpoint. But again, this is off-topic and unlikely possible.
>

What's wrong with off-topic? :)

As vvar demonstrates, it's possible to add new per-process vmas that
show up in all processes automatically.  The trickiest part is making
it work with CRIU.

--Andy

> Oleg.
>



-- 
Andy Lutomirski
AMA Capital Management, LLC
--
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/