linux-kernel - Re: [Announce] Checkpoint-restore tool v0.1

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: <CAFLxGvxgq9HJJvRgz=z48D7V_j=dTv4jSCLqEZcE=oCBAXnSug@mail.gmail.com>
Date:	Tue, 31 Jul 2012 12:21:58 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Cyrill Gorcunov <gorcunov@...nvz.org>
Cc:	Pavel Emelyanov <xemul@...allels.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"lwn@....net" <lwn@....net>, "criu@...nvz.org" <criu@...nvz.org>,
	"users@...nvz.org" <users@...nvz.org>,
	Containers <containers@...ts.linux-foundation.org>,
	cgroups mailinglist <cgroups@...r.kernel.org>
Subject: Re: [Announce] Checkpoint-restore tool v0.1

On Tue, Jul 31, 2012 at 12:16 PM, Cyrill Gorcunov <gorcunov@...nvz.org> wrote:
> On Tue, Jul 31, 2012 at 12:08:22PM +0200, richard -rw- weinberger wrote:
>> On Tue, Jul 31, 2012 at 11:54 AM, Pavel Emelyanov <xemul@...allels.com> wrote:
>> >> Yeah, but I fear it's not that easy.
>> >> We'd have to change crtools to work without ptrace().
>> >
>> > Well, this is hard. Using ptrace saved us from having many special-purpose
>> > APIs for dumping various stuff (there will be an article about it). Thus I
>> > don't know which way is simpler -- stop using ptrace or teach ptrece to allow
>> > several tracers to attach to one task %)
>>
>> Allowing multiple tracers in a safe way is IMHO even more harder.
>>
>> BTW:  While reading prctl_set_mm() I noticed two things.
>> 1.  Why isn't the return value of find_vma() verified?
>
> prctl_set_mm
>         vma = find_vma(mm, addr);
>         ...
>         if (!vma) {
>                 error = -EFAULT;
>                 goto out;
>         }
>
> these values are used in procfs statistics only. So I don't get
> which verify you mean here.

If I do PR_SET_MM_START_BRK the if(!vma) will never be executed because
there a break in case PR_SET_MM_START_BRK.

-- 
Thanks,
//richard
--
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/