diff for duplicates of <1505466569.4200.88.camel@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 4ad05ab..60f068f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -7,7 +7,7 @@ On Fri, 2017-09-15 at 05:04 -0400, Mimi Zohar wrote: > > > Why should a read need exclusive access? You'd think shared is sufficient. > -> True, reading a file shouldn't require an exclusive lock. ?The +> True, reading a file shouldn't require an exclusive lock. The > exclusive lock is taken to prevent the file from changing while the > file hash is being calculated. @@ -17,15 +17,15 @@ times. > > > But regardless, it needs *explanation*. > -> Agreed. ?A fuller explanation was included in the cover letter that -> should have also been included in the patch description. ?The +> Agreed. A fuller explanation was included in the cover letter that +> should have also been included in the patch description. The > following is taken from the cover letter: > > With the introduction of IMA-appraisal and the need to write file > hashes as security xattrs, IMA needed to take the global i_mutex -> lock.??process_measurement() took the iint->mutex first and then +> lock. process_measurement() took the iint->mutex first and then > the i_mutex, while setxattr, chmod and chown took the locks in -> reverse order.??To resolve this potential deadlock, the iint->mutex +> reverse order. To resolve this potential deadlock, the iint->mutex > was removed. > > Some filesystems have recently replaced their filesystem dependent @@ -45,9 +45,9 @@ times. > > says it is > > > > So no, this needs more work. -> >? -> >?????Linus -> >? +> > +> > Linus +> > > > > > > On Sep 14, 2017 21:59, "Mimi Zohar" <zohar@linux.vnet.ibm.com> wrote: @@ -394,11 +394,6 @@ times. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-security-module" in -> the body of a message to majordomo at vger.kernel.org +> the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -> - --- -To unsubscribe from this list: send the line "unsubscribe linux-security-module" in -the body of a message to majordomo at vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html +> diff --git a/a/content_digest b/N1/content_digest index 5e49f62..e6083dc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,10 +2,33 @@ "ref\01505451494-30228-4-git-send-email-zohar@linux.vnet.ibm.com\0" "ref\0CA+55aFwVujvsdaq09O216u-uBbBbo5i_1d6aw3ksottR_uiJ6w@mail.gmail.com\0" "ref\01505466296.4200.86.camel@linux.vnet.ibm.com\0" - "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0" - "Subject\0[PATCH 3/3] ima: use fs method to read integrity data\0" + "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" + "Subject\0Re: [PATCH 3/3] ima: use fs method to read integrity data\0" "Date\0Fri, 15 Sep 2017 05:09:29 -0400\0" - "To\0linux-security-module@vger.kernel.org\0" + "To\0Linus Torvalds <torvalds@linux-foundation.org>\0" + "Cc\0Dave Kleikamp <shaggy@kernel.org>" + Bob Peterson <rpeterso@redhat.com> + David Woodhouse <dwmw2@infradead.org> + Chao Yu <yuchao0@huawei.com> + Hugh Dickins <hughd@google.com> + Darrick J. Wong <darrick.wong@oracle.com> + Matthew Garrett <mjg59@srcf.ucam.org> + Joel Becker <jlbec@evilplan.org> + Jan Kara <jack@suse.com> + Chris Mason <clm@fb.com> + Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> + Steven Whitehouse <swhiteho@redhat.com> + Christoph Hellwig <hch@infradead.org> + Andreas Dilger <adilger.kernel@dilger.ca> + Theodore Ts'o <tytso@mit.edu> + Mark Fasheh <mfasheh@versity.com> + linux-security-module@vger.kernel.org + linux-ima-devel@lists.sourceforge.net + James Morris <jmorris@namei.org> + Richard Weinberger <richard@nod.at> + Jaegeuk Kim <jaegeuk@kernel.org> + Linux Kernel Mailing List <linux-kernel@vger.kernel.org> + " Christoph Hellwig <hch@lst.de>\0" "\00:1\0" "b\0" "On Fri, 2017-09-15 at 05:04 -0400, Mimi Zohar wrote:\n" @@ -17,7 +40,7 @@ "> \n" "> > Why should a read need exclusive access? You'd think shared is sufficient.\n" "> \n" - "> True, reading a file shouldn't require an exclusive lock. ?The\n" + "> True, reading a file shouldn't require an exclusive lock. \302\240The\n" "> exclusive lock is taken to prevent the file from changing while the\n" "> file hash is being calculated.\n" "\n" @@ -27,15 +50,15 @@ "> \n" "> > But regardless, it needs *explanation*.\n" "> \n" - "> Agreed. ?A fuller explanation was included in the cover letter that\n" - "> should have also been included in the patch description. ?The\n" + "> Agreed. \302\240A fuller explanation was included in the cover letter that\n" + "> should have also been included in the patch description. \302\240The\n" "> following is taken from the cover letter:\n" "> \n" "> With the introduction of IMA-appraisal and the need to write file\n" "> hashes as security xattrs, IMA needed to take the global i_mutex\n" - "> lock.??process_measurement() took the iint->mutex first and then\n" + "> lock.\302\240\302\240process_measurement() took the iint->mutex first and then\n" "> the i_mutex, while setxattr, chmod and chown took the locks in\n" - "> reverse order.??To resolve this potential deadlock, the iint->mutex\n" + "> reverse order.\302\240\302\240To resolve this potential deadlock, the iint->mutex\n" "> was removed.\n" "> \n" "> Some filesystems have recently replaced their filesystem dependent\n" @@ -55,9 +78,9 @@ "> > says it is\n" "> > \n" "> > So no, this needs more work.\n" - "> >?\n" - "> >?????Linus\n" - "> >?\n" + "> >\302\240\n" + "> >\302\240\302\240\302\240\302\240\302\240Linus\n" + "> >\302\240\n" "> \n" "> > \n" "> > On Sep 14, 2017 21:59, \"Mimi Zohar\" <zohar@linux.vnet.ibm.com> wrote:\n" @@ -404,13 +427,8 @@ "> \n" "> --\n" "> To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n" - "> the body of a message to majordomo at vger.kernel.org\n" + "> the body of a message to majordomo@vger.kernel.org\n" "> More majordomo info at http://vger.kernel.org/majordomo-info.html\n" - "> \n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n" - "the body of a message to majordomo at vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + > -e2a76735e1b9d580ecc2a3149b6655f2a20ef1892e7d67ca871e192673a856d0 +af8f2ec8f7ad87014a6facef4c8522e473873a6747828f84286ac0411184dae5
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.