From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Artem Fetishev <artem_fetishev@epam.com>,
akpm@linux-foundation.org, 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:45:00 +0400 [thread overview]
Message-ID: <20140307144500.GI1852@moon> (raw)
In-Reply-To: <5319D7B9.6050000@parallels.com>
On Fri, Mar 07, 2014 at 06:29:13PM +0400, Pavel Emelyanov wrote:
> 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>
Good catch, thanks!
Acked-by: Cyrill Gorcunov <gorcunov@openvz.org>
I suppose this is a stable@ material.
next prev parent reply other threads:[~2014-03-07 14:45 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
2014-03-07 14:45 ` Cyrill Gorcunov [this message]
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=20140307144500.GI1852@moon \
--to=gorcunov@gmail.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 \
--cc=xemul@parallels.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