The brlock was completely removed in the 3.13 kernel series.
see commit 0f6ed63b1707 ("no need to keep brlock macros anymore...")It seems that documentation in seqlock.h was not updated to reflect this. This patch drops the (hopefully last) false brlock reference. All remaining references to brlock refer to byte-range locks (notably in cifs) and not to "Big Reader Lock" and should be correct. patch is against 3.19.0-rc1 linux-next Signed-off-by: Nicholas Mc Guire <[email protected]> --- include/linux/seqlock.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h index f5df8f6..af7f5e9 100644 --- a/include/linux/seqlock.h +++ b/include/linux/seqlock.h @@ -13,9 +13,8 @@ * from going forward. Unlike the regular rwlock, the read lock here is * exclusive so that only one locking reader can get it. * - * This is not as cache friendly as brlock. Also, this may not work well - * for data that contains pointers, because any writer could - * invalidate a pointer that a reader was following. + * This may not work well for data that contains pointers, because any + * writer could invalidate a pointer that a reader was following. * * Expected non-blocking reader usage: * do { -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
