linux-kernel - Re: [PATCH v7 1/2] mm: introduce process

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: <YQzZSmRqYmxFJ61y@dhcp22.suse.cz>
Date:   Fri, 6 Aug 2021 08:40:10 +0200
From:   Michal Hocko <mhocko@...e.com>
To:     Suren Baghdasaryan <surenb@...gle.com>
Cc:     akpm@...ux-foundation.org, rientjes@...gle.com,
        willy@...radead.org, hannes@...xchg.org, guro@...com,
        riel@...riel.com, minchan@...nel.org, christian@...uner.io,
        hch@...radead.org, oleg@...hat.com, david@...hat.com,
        jannh@...gle.com, shakeelb@...gle.com, luto@...nel.org,
        christian.brauner@...ntu.com, fweimer@...hat.com, jengelh@...i.de,
        timmurray@...gle.com, linux-api@...r.kernel.org,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        kernel-team@...roid.com
Subject: Re: [PATCH v7 1/2] mm: introduce process_mrelease system call

On Thu 05-08-21 10:08:58, Suren Baghdasaryan wrote:
[...]
> +	/*
> +	 * If the task is dying and in the process of releasing its memory
> +	 * then get its mm.
> +	 */
> +	p = find_lock_task_mm(task);
> +	if (!p) {
> +		ret = -ESRCH;
> +		goto put_pid;
> +	}
> +	if (task != p) {
> +		get_task_struct(p);
> +		put_task_struct(task);
> +		task = p;
> +	}

Why do you need to take a reference to the p here? You are under
task_lock so this will not go away and you only need p to get your mm.

> +
> +	/* If the work has been done already, just exit with success */
> +	if (test_bit(MMF_OOM_SKIP, &task->mm->flags))
> +		goto put_task;

You want to release the task_lock

> +
> +	if (task_will_free_mem(task) && (task->flags & PF_KTHREAD) == 0) {

you want task_will_free_mem(p) and what is the point of the PF_KTHREAD
check?

> +		mm = task->mm;
> +		mmget(mm);

All you need is to make sure mm will not get released under your feet
once task_lock is released so mmgrab is the right thing to do here. The
address space can be torn down in parallel and that is OK and desirable.

I think you really want something like this:

	if (flags)
		return -EINVAL;
	
	pid = pidfd_get_pid(fd, &f_flags);
	if (IS_ERR(pid))
		return PTR_ERR(pid);
	task = get_pid_task(pid, PIDTYPE_PID);
	if (!task) {
		ret = -ESRCH;
		goto put_pid;
	}

	/*
	 * Make sure to chose a thread which still has a reference to mm
	 * during the group exit
	 */
	p = find_lock_task_mm(task);
	if (!p) {
		ret = -ESRCH;
		goto put_task;
	}

	mm = task->mm;
	mmgrab(mm);
	reap = true;
	/* If the work has been done already, just exit with success */
	if (test_bit(MMF_OOM_SKIP, &mm->flags)) {
		reap = false;
	} else if (!task_will_free_mem(p)) {
		reap = false;
		ret = -EINVAL;
	}
	task_unlock(p);

	if (!reap)
		goto dropmm;;

	/* Do the work*/


dropmm:
	mmdrop(mm);
put_task:
	put_task(task);
put_pid:
	put_pid(pid);

	return ret;

-- 
Michal Hocko
SUSE Labs