diff for duplicates of <20171002043554.GI15067@dastard> diff --git a/a/1.txt b/N1/1.txt index 1372d79..582f77a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -36,7 +36,7 @@ regardless of the number of writes performed to that file. That's why NFS can't use it as a change attribute, and hence we have i_version.... -> Now, even more recently, I received a patch that claims that +> ?Now, even more recently, I received a patch that claims that > i_version is just a performance improvement. Did you ask them to explain/quantify the performance improvement? @@ -48,7 +48,7 @@ We take that penalty because NFS requires specific change attribute behaviour, otherwise we wouldn't have implemented it at all in XFS... -> For file systems that +> ?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 @@ -84,7 +84,7 @@ ima_check_last_writer -> ima_collect_measurement -> ima_fix_xattr -> 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). @@ -99,7 +99,7 @@ lock and call ima_update_xattr(). The sampled i_version then tells us if the file has changed before we write the updated xattr... > 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. ima_collect_measurement() doesn't write an xattr at all - it just @@ -121,4 +121,8 @@ Cheers, Dave. -- Dave Chinner -david@fromorbit.com +david at fromorbit.com +-- +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 bbb5c19..c452974 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,20 +8,10 @@ "ref\0CA+55aFwG65-1DZGLkxWzXiPHECjVvY+WHa0ihRq6MbJ4yrX-Sg@mail.gmail.com\0" "ref\020171001223402.GG15067@dastard\0" "ref\01506901362.5691.247.camel@linux.vnet.ibm.com\0" - "From\0Dave Chinner <david@fromorbit.com>\0" - "Subject\0Re: [RFC PATCH 3/3] fs: detect that the i_rwsem has already been taken exclusively\0" + "From\0david@fromorbit.com (Dave Chinner)\0" + "Subject\0[RFC PATCH 3/3] fs: detect that the i_rwsem has already been taken exclusively\0" "Date\0Mon, 2 Oct 2017 15:35:54 +1100\0" - "To\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Cc\0Linus Torvalds <torvalds@linux-foundation.org>" - Eric W. Biederman <ebiederm@xmission.com> - 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" "On Sun, Oct 01, 2017 at 07:42:42PM -0400, Mimi Zohar wrote:\n" @@ -62,7 +52,7 @@ "why NFS can't use it as a change attribute, and hence we have\n" "i_version....\n" "\n" - "> Now, even more recently, I received a patch that claims that\n" + "> ?Now, even more recently, I received a patch that claims that\n" "> i_version is just a performance improvement.\n" "\n" "Did you ask them to explain/quantify the performance improvement? \n" @@ -74,7 +64,7 @@ "behaviour, otherwise we wouldn't have implemented it at all in\n" "XFS...\n" "\n" - "> For file systems that\n" + "> ?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" @@ -110,7 +100,7 @@ " -> ima_collect_measurement\n" " -> ima_fix_xattr\n" "\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" @@ -125,7 +115,7 @@ "us if the file has changed before we write the updated xattr...\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" "ima_collect_measurement() doesn't write an xattr at all - it just\n" @@ -147,6 +137,10 @@ "Dave.\n" "-- \n" "Dave Chinner\n" - david@fromorbit.com + "david at fromorbit.com\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 -6eee011950e39f4778de64ff7b7d8e61bc033bf89a8e8253a110893cf984c067 +dc66a426de7f762677968437da8dac802441ed13ba0f64f44119a924fe136749
diff --git a/a/1.txt b/N2/1.txt index 1372d79..d5243d6 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -36,7 +36,7 @@ regardless of the number of writes performed to that file. That's why NFS can't use it as a change attribute, and hence we have i_version.... -> Now, even more recently, I received a patch that claims that +> �Now, even more recently, I received a patch that claims that > i_version is just a performance improvement. Did you ask them to explain/quantify the performance improvement? @@ -48,7 +48,7 @@ We take that penalty because NFS requires specific change attribute behaviour, otherwise we wouldn't have implemented it at all in XFS... -> For file systems that +> �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 @@ -84,7 +84,7 @@ ima_check_last_writer -> ima_collect_measurement -> ima_fix_xattr -> 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). @@ -99,7 +99,7 @@ lock and call ima_update_xattr(). The sampled i_version then tells us if the file has changed before we write the updated xattr... > 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. ima_collect_measurement() doesn't write an xattr at all - it just diff --git a/a/content_digest b/N2/content_digest index bbb5c19..5219caa 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -62,7 +62,7 @@ "why NFS can't use it as a change attribute, and hence we have\n" "i_version....\n" "\n" - "> Now, even more recently, I received a patch that claims that\n" + "> \303\257\302\277\302\275Now, even more recently, I received a patch that claims that\n" "> i_version is just a performance improvement.\n" "\n" "Did you ask them to explain/quantify the performance improvement? \n" @@ -74,7 +74,7 @@ "behaviour, otherwise we wouldn't have implemented it at all in\n" "XFS...\n" "\n" - "> For file systems that\n" + "> \303\257\302\277\302\275For 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" @@ -110,7 +110,7 @@ " -> ima_collect_measurement\n" " -> ima_fix_xattr\n" "\n" - "> ima_collect_measurement() calculates the file hash for storing in the\n" + "> \303\257\302\277\302\275ima_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" @@ -125,7 +125,7 @@ "us if the file has changed before we write the updated xattr...\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. \303\257\302\277\302\275Writing the xattr will need to be deferred until after\n" "> the iint->mutex is released.\n" "\n" "ima_collect_measurement() doesn't write an xattr at all - it just\n" @@ -149,4 +149,4 @@ "Dave Chinner\n" david@fromorbit.com -6eee011950e39f4778de64ff7b7d8e61bc033bf89a8e8253a110893cf984c067 +d92dc623720adf74555f1fe5132c45782ae30830d777f453a2f073003053ded3
diff --git a/a/1.txt b/N3/1.txt index 1372d79..024d034 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -36,7 +36,7 @@ regardless of the number of writes performed to that file. That's why NFS can't use it as a change attribute, and hence we have i_version.... -> Now, even more recently, I received a patch that claims that +> Now, even more recently, I received a patch that claims that > i_version is just a performance improvement. Did you ask them to explain/quantify the performance improvement? @@ -48,7 +48,7 @@ We take that penalty because NFS requires specific change attribute behaviour, otherwise we wouldn't have implemented it at all in XFS... -> For file systems that +> 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 @@ -84,7 +84,7 @@ ima_check_last_writer -> ima_collect_measurement -> ima_fix_xattr -> 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). @@ -99,7 +99,7 @@ lock and call ima_update_xattr(). The sampled i_version then tells us if the file has changed before we write the updated xattr... > 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. ima_collect_measurement() doesn't write an xattr at all - it just diff --git a/a/content_digest b/N3/content_digest index bbb5c19..2b8af85 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -62,7 +62,7 @@ "why NFS can't use it as a change attribute, and hence we have\n" "i_version....\n" "\n" - "> Now, even more recently, I received a patch that claims that\n" + "> \302\240Now, even more recently, I received a patch that claims that\n" "> i_version is just a performance improvement.\n" "\n" "Did you ask them to explain/quantify the performance improvement? \n" @@ -74,7 +74,7 @@ "behaviour, otherwise we wouldn't have implemented it at all in\n" "XFS...\n" "\n" - "> For file systems that\n" + "> \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" @@ -110,7 +110,7 @@ " -> ima_collect_measurement\n" " -> ima_fix_xattr\n" "\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" @@ -125,7 +125,7 @@ "us if the file has changed before we write the updated xattr...\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" "ima_collect_measurement() doesn't write an xattr at all - it just\n" @@ -149,4 +149,4 @@ "Dave Chinner\n" david@fromorbit.com -6eee011950e39f4778de64ff7b7d8e61bc033bf89a8e8253a110893cf984c067 +86bd57f407c55fc182a7ebd6caee201543c36c4edfb4543286cc8fc39017e698
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.