diff for duplicates of <87ehaolz8v.fsf@xmission.com> diff --git a/a/1.txt b/N1/1.txt index 942fc2e..0dee732 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ -"Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org> writes: +"Serge E. Hallyn" <serge@hallyn.com> writes: -> Quoting Serge E. Hallyn (serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org): ->> Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org): +> Quoting Serge E. Hallyn (serge@hallyn.com): +>> Quoting Eric W. Biederman (ebiederm@xmission.com): >> > >> > Serge does this patch break lxc? I think all should be well but I want >> > to make certain there is not some hidden case where this fundamentaly @@ -19,7 +19,7 @@ Just to confirm. Can you do a lazy umount of put_old and get rid of them? -> Acked-by: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org> +> Acked-by: Serge Hallyn <serge.hallyn@canonical.com> > > ( Mind you I'm not approving of the idea of hiding mounts as a security > mechanisms, but I know that neither are you :) diff --git a/a/content_digest b/N1/content_digest index 511681c..d8fed7d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,21 +3,20 @@ "ref\087li4wpi2b.fsf@xmission.com\0" "ref\020130724124933.GA16517@mail.hallyn.com\0" "ref\020130724153018.GA17960@mail.hallyn.com\0" - "ref\020130724153018.GA17960-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org\0" - "From\0ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)\0" + "From\0ebiederm@xmission.com (Eric W. Biederman)\0" "Subject\0Re: [REVIEW][PATCH] vfs: Lock in place mounts from more privileged users\0" "Date\0Wed, 24 Jul 2013 09:05:36 -0700\0" - "To\0Serge E. Hallyn <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>\0" - "Cc\0linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - Linux Containers <containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org> - linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org - " Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>\0" + "To\0Serge E. Hallyn <serge@hallyn.com>\0" + "Cc\0Andy Lutomirski <luto@amacapital.net>" + Linux Containers <containers@lists.linux-foundation.org> + linux-kernel@vger.kernel.org + " linux-fsdevel@vger.kernel.org\0" "\00:1\0" "b\0" - "\"Serge E. Hallyn\" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org> writes:\n" + "\"Serge E. Hallyn\" <serge@hallyn.com> writes:\n" "\n" - "> Quoting Serge E. Hallyn (serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org):\n" - ">> Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):\n" + "> Quoting Serge E. Hallyn (serge@hallyn.com):\n" + ">> Quoting Eric W. Biederman (ebiederm@xmission.com):\n" ">> > \n" ">> > Serge does this patch break lxc? I think all should be well but I want\n" ">> > to make certain there is not some hidden case where this fundamentaly\n" @@ -35,7 +34,7 @@ "Just to confirm. Can you do a lazy umount of put_old and get rid of\n" "them?\n" "\n" - "> Acked-by: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>\n" + "> Acked-by: Serge Hallyn <serge.hallyn@canonical.com>\n" ">\n" "> ( Mind you I'm not approving of the idea of hiding mounts as a security\n" "> mechanisms, but I know that neither are you :)\n" @@ -49,4 +48,4 @@ "\n" Eric -d559e23fbba524a81ac5b2fe418fdc6999b9b74da3cbb337bf2e91e183a26c57 +4f6adc45833462db66db12fb07fe015b8f36e9b80b11572f87b6defb753341f7
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.