From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [PATCH] proc: revalidate dentry returned by proc_pid_follow_link Date: Sun, 08 Nov 2009 19:30:55 -0800 Message-ID: References: <1257513594-31071-1-git-send-email-jlayton@redhat.com> <20091106203601.GD27751@shareable.org> <20091106160612.4cd05e76@tlielax.poochiereds.net> <20091108201237.79af5cac@tupile.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jamie Lokier , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, adobriyan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org To: Jeff Layton Return-path: In-Reply-To: <20091108201237.79af5cac-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org> (Jeff Layton's message of "Sun\, 8 Nov 2009 20\:12\:37 -0500") Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Jeff Layton writes: >> Hmm. Looking at the code I get the impression that a file bind mount >> will have exactly the same problem. >> >> Can you confirm. >> >> If file bind mounts also have this problem a bugfix to to just >> proc seems questionable. >> > > I'm not sure I understand what you mean by "file bind mount". Is that > something like mounting with "-o loop" ? # cd /tmp # echo foo > foo # echo bar > bar # mount --bind foo bar # cat bar foo # > I'm not at all opposed to fixing this in a more broad fashion, but as > best I can tell, the only place that LAST_BIND is used is in procfs. proc does appear to be the only user of LAST_BIND. With a file bind mount we can get to the same ok: label without a revalidate. The difference is that we came from __follow_mount instead of follow_link. At least that is how I read the code. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html