From: Andrew Morton <akpm@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Valdis.Kletnieks@vt.edu, hugh.dickins@tiscali.co.uk,
matthew@wil.cx, agruen@suse.de, viro@zeniv.linux.org.uk,
hch@lst.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] vfs: no "(unreachable)" prefix for SYSVIPC maps in /proc/PID/maps
Date: Wed, 9 Sep 2009 14:24:03 -0700 [thread overview]
Message-ID: <20090909142403.c3b35d4d.akpm@linux-foundation.org> (raw)
In-Reply-To: <E1Mkg2P-0000mi-H3@pomaz-ex.szeredi.hu>
On Mon, 07 Sep 2009 17:21:49 +0200
Miklos Szeredi <miklos@szeredi.hu> wrote:
> Another fix for vfs-fix-d_path-for-unreachable-paths.patch in -mm.
>
Now I'm confused.
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> The patch
>
> "vfs: fix d_path() for unreachable paths"
>
> generally changed d_path() to report unreachable paths with a special
> prefix. This has an effect on /proc/${PID}/maps as well for memory
> maps set up with shmem_file_setup() or hugetlb_file_setup(). These
> functions set up unlinked files under a kernel-private vfsmount.
> Since this vfsmount is unreachable from userspace, these maps will be
> reported with the "(unreachable)" prefix.
>
> This is undesirable, because it changes the kernel ABI and might break
> applications for no good reason.
>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
These three patches are fixes against
vfs-fix-d_path-for-unreachable-paths.patch? The description for
seq_file-return-a-negative-error-code-when-seq_path_root-fails.patch
led me to believe that vfs-fix-d_path-for-unreachable-paths.patch was
to be dropped.
argh.
next prev parent reply other threads:[~2009-09-09 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 15:21 Miklos Szeredi
2009-09-08 18:04 ` Hugh Dickins
2009-09-09 21:24 ` Andrew Morton [this message]
2009-09-10 5:43 ` Miklos Szeredi
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=20090909142403.c3b35d4d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=agruen@suse.de \
--cc=hch@lst.de \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®