public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels.com>
To: Artem Fetishev <artem_fetishev@epam.com>, <akpm@linux-foundation.org>
Cc: <containers@lists.linux-foundation.org>,
	<linux-kernel@vger.kernel.org>, <wiebittewas@googlemail.com>,
	<alexandr_terekhov@epam.com>
Subject: Re: [PATCH] proc: #68991 Fix GPF in /proc/$PID/map_files
Date: Fri, 7 Mar 2014 18:29:13 +0400	[thread overview]
Message-ID: <5319D7B9.6050000@parallels.com> (raw)
In-Reply-To: <20140308022033.GC5690@owamsq.epam.com>

On 03/08/2014 06:20 AM, Artem Fetishev wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=68991
> 
> The expected logic of proc_map_files_get_link() is either to return 0 and
> initialize 'path' or return an error and leave 'path' uninitialized. By the time
> dname_to_vma_addr() returns 0 the corresponding vma may have already be gone. In
> this case the path is not initialized but the return value is still 0. This
> results in 'general protection fault' inside d_path().
> 
> Steps to reproduce:
> CONFIG_CHECKPOINT_RESTORE=y
> 
> fd = open(...);
> while (1) {
> 	mmap(fd, ...);
> 	munmap(fd, ...);
> }
> 
> ls -la /proc/$PID/map_files
> 
> Signed-off-by: Artem Fetishev <artem_fetishev@epam.com>
> Signed-off-by: Aleksandr Terekhov <aleksandr_terekhov@epam.com>

Acked-by: Pavel Emelyanov <xemul@parallels.com>


> ---
> diff --git a/fs/proc/base.c b/fs/proc/base.c
> index 5150706..b976062 100644
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -1824,6 +1824,7 @@ static int proc_map_files_get_link(struct dentry *dentry, struct path *path)
>  	if (rc)
>  		goto out_mmput;
>  
> +	rc = -ENOENT;
>  	down_read(&mm->mmap_sem);
>  	vma = find_exact_vma(mm, vm_start, vm_end);
>  	if (vma && vma->vm_file) {
> .
> 



  reply	other threads:[~2014-03-07 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08  2:20 [PATCH] proc: #68991 Fix GPF in /proc/$PID/map_files Artem Fetishev
2014-03-07 14:29 ` Pavel Emelyanov [this message]
2014-03-07 14:45   ` Cyrill Gorcunov
2014-03-07 20:17 ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5319D7B9.6050000@parallels.com \
    --to=xemul@parallels.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexandr_terekhov@epam.com \
    --cc=artem_fetishev@epam.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wiebittewas@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox