diff for duplicates of <20161222090652.GA8715@infradead.org> diff --git a/a/1.txt b/N1/1.txt index cad5329..262ca05 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Thu, Dec 22, 2016 at 09:58:42AM +0100, Micka�l Sala�n wrote: +On Thu, Dec 22, 2016 at 09:58:42AM +0100, Mickaël Salaün wrote: > Of course a read-only mount point can do the trick (except for anonymous > inodes). However, a security policy (e.g. for SELinux) should not (and > can't always) rely on mount options. For example, a security policy can diff --git a/a/content_digest b/N1/content_digest index db0fa69..6aa12d6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -29,7 +29,7 @@ " Christoph Hellwig <hch@infradead.org>\0" "\00:1\0" "b\0" - "On Thu, Dec 22, 2016 at 09:58:42AM +0100, Micka\303\257\302\277\302\275l Sala\303\257\302\277\302\275n wrote:\n" + "On Thu, Dec 22, 2016 at 09:58:42AM +0100, Micka\303\253l Sala\303\274n wrote:\n" "> Of course a read-only mount point can do the trick (except for anonymous\n" "> inodes). However, a security policy (e.g. for SELinux) should not (and\n" "> can't always) rely on mount options. For example, a security policy can\n" @@ -45,4 +45,4 @@ "A security policy must not mess with the readonly state of a file system\n" or mount, period. You're overstepping your boundaries. -97c0923104d2e16e1df5713cbb34fdd4e6f0b3315812d41e9339bf3a2d71f8ad +201f96cabecef8024109722e672459b035c23652a0b6705cc73c1c5f94ca4b35
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.