diff for duplicates of <87zi9ai63l.fsf@xmission.com> diff --git a/a/1.txt b/N1/1.txt index bf064ee..972bc57 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -30,8 +30,8 @@ Mimi Zohar <zohar@linux.vnet.ibm.com> writes: >> ATM). > > Recently I received a patch to replace i_version with mtime/atime. -> Now, even more recently, I received a patch that claims that -> i_version is just a performance improvement. For file systems that +> ?Now, even more recently, I received a patch that claims that +> i_version is just a performance improvement. ?For file systems that > don't support i_version, assume that the file has changed. > > For file systems that don't support i_version, instead of assuming @@ -53,12 +53,12 @@ Mimi Zohar <zohar@linux.vnet.ibm.com> writes: > > The security.ima xattr is normally written out in > ima_check_last_writer(), not in ima_collect_measurement(). -> ima_collect_measurement() calculates the file hash for storing in the +> ?ima_collect_measurement() calculates the file hash for storing in the > measurement list (IMA-measurement), verifying the hash/signature (IMA- > appraisal) already stored in the xattr, and auditing (IMA-audit). > > The only time that ima_collect_measurement() writes the file xattr is -> in "fix" mode. Writing the xattr will need to be deferred until after +> in "fix" mode. ?Writing the xattr will need to be deferred until after > the iint->mutex is released. > > There should be no open writers in ima_check_last_writer(), so the @@ -72,3 +72,7 @@ Do you not support such systems or do you have a sufficient way to detect changes? Eric +-- +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 588dde4..678d578 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,19 +11,9 @@ "ref\020171001223402.GG15067@dastard\0" "ref\01506901362.5691.247.camel@linux.vnet.ibm.com\0" "From\0ebiederm@xmission.com (Eric W. Biederman)\0" - "Subject\0Re: [RFC PATCH 3/3] fs: detect that the i_rwsem has already been taken exclusively\0" + "Subject\0[RFC PATCH 3/3] fs: detect that the i_rwsem has already been taken exclusively\0" "Date\0Sun, 01 Oct 2017 22:25:18 -0500\0" - "To\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Cc\0Dave Chinner <david@fromorbit.com>" - Linus Torvalds <torvalds@linux-foundation.org> - LSM List <linux-security-module@vger.kernel.org> - linux-fsdevel <linux-fsdevel@vger.kernel.org> - Christoph Hellwig <hch@infradead.org> - Theodore Ts'o <tytso@mit.edu> - Jan Kara <jack@suse.cz> - Linux Kernel Mailing List <linux-kernel@vger.kernel.org> - linux-integrity@vger.kernel.org - " Sascha Hauer <s.hauer@pengutronix.de>\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "Mimi Zohar <zohar@linux.vnet.ibm.com> writes:\n" @@ -58,8 +48,8 @@ ">> ATM).\n" ">\n" "> Recently I received a patch to replace i_version with mtime/atime.\n" - "> Now, even more recently, I received a patch that claims that\n" - "> i_version is just a performance improvement. For file systems that\n" + "> ?Now, even more recently, I received a patch that claims that\n" + "> i_version is just a performance improvement. ?For file systems that\n" "> don't support i_version, assume that the file has changed.\n" ">\n" "> For file systems that don't support i_version, instead of assuming\n" @@ -81,12 +71,12 @@ ">\n" "> The security.ima xattr is normally written out in\n" "> ima_check_last_writer(), not in ima_collect_measurement().\n" - "> ima_collect_measurement() calculates the file hash for storing in the\n" + "> ?ima_collect_measurement() calculates the file hash for storing in the\n" "> measurement list (IMA-measurement), verifying the hash/signature (IMA-\n" "> appraisal) already stored in the xattr, and auditing (IMA-audit).\n" ">\n" "> The only time that ima_collect_measurement() writes the file xattr is\n" - "> in \"fix\" mode. Writing the xattr will need to be deferred until after\n" + "> in \"fix\" mode. ?Writing the xattr will need to be deferred until after\n" "> the iint->mutex is released.\n" ">\n" "> There should be no open writers in ima_check_last_writer(), so the\n" @@ -99,6 +89,10 @@ "Do you not support such systems or do you have a sufficient way to\n" "detect changes?\n" "\n" - Eric + "Eric\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 -b95efe7fc1c69b71e7ef90c2267e091e573a9dd1313c4edc3e22d57e35a3a082 +ff0a3f7342e87b391e0082efa339d17802f991029626f64c356e661c8869572d
diff --git a/a/1.txt b/N2/1.txt index bf064ee..6179e9d 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -30,8 +30,8 @@ Mimi Zohar <zohar@linux.vnet.ibm.com> writes: >> ATM). > > Recently I received a patch to replace i_version with mtime/atime. -> Now, even more recently, I received a patch that claims that -> i_version is just a performance improvement. For file systems that +> Now, even more recently, I received a patch that claims that +> i_version is just a performance improvement. For file systems that > don't support i_version, assume that the file has changed. > > For file systems that don't support i_version, instead of assuming @@ -53,12 +53,12 @@ Mimi Zohar <zohar@linux.vnet.ibm.com> writes: > > The security.ima xattr is normally written out in > ima_check_last_writer(), not in ima_collect_measurement(). -> ima_collect_measurement() calculates the file hash for storing in the +> ima_collect_measurement() calculates the file hash for storing in the > measurement list (IMA-measurement), verifying the hash/signature (IMA- > appraisal) already stored in the xattr, and auditing (IMA-audit). > > The only time that ima_collect_measurement() writes the file xattr is -> in "fix" mode. Writing the xattr will need to be deferred until after +> in "fix" mode. Writing the xattr will need to be deferred until after > the iint->mutex is released. > > There should be no open writers in ima_check_last_writer(), so the diff --git a/a/content_digest b/N2/content_digest index 588dde4..e85458f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -58,8 +58,8 @@ ">> ATM).\n" ">\n" "> Recently I received a patch to replace i_version with mtime/atime.\n" - "> Now, even more recently, I received a patch that claims that\n" - "> i_version is just a performance improvement. For file systems that\n" + "> \302\240Now, even more recently, I received a patch that claims that\n" + "> i_version is just a performance improvement. \302\240For file systems that\n" "> don't support i_version, assume that the file has changed.\n" ">\n" "> For file systems that don't support i_version, instead of assuming\n" @@ -81,12 +81,12 @@ ">\n" "> The security.ima xattr is normally written out in\n" "> ima_check_last_writer(), not in ima_collect_measurement().\n" - "> ima_collect_measurement() calculates the file hash for storing in the\n" + "> \302\240ima_collect_measurement() calculates the file hash for storing in the\n" "> measurement list (IMA-measurement), verifying the hash/signature (IMA-\n" "> appraisal) already stored in the xattr, and auditing (IMA-audit).\n" ">\n" "> The only time that ima_collect_measurement() writes the file xattr is\n" - "> in \"fix\" mode. Writing the xattr will need to be deferred until after\n" + "> in \"fix\" mode. \302\240Writing the xattr will need to be deferred until after\n" "> the iint->mutex is released.\n" ">\n" "> There should be no open writers in ima_check_last_writer(), so the\n" @@ -101,4 +101,4 @@ "\n" Eric -b95efe7fc1c69b71e7ef90c2267e091e573a9dd1313c4edc3e22d57e35a3a082 +fba05fcfa787628c048855ced63fcbde4e9148d518ebbaf04af68514360d4c5b
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.