From d4e493caf788ef44982e131ff9c786546904d934 Mon Sep 17 00:00:00 2001 From: André Fabian Silva Delgado Date: Fri, 11 Mar 2016 18:08:49 -0300 Subject: Linux-libre 4.4.5-gnu --- fs/jffs2/README.Locking | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'fs/jffs2/README.Locking') diff --git a/fs/jffs2/README.Locking b/fs/jffs2/README.Locking index 3ea365541..8918ac905 100644 --- a/fs/jffs2/README.Locking +++ b/fs/jffs2/README.Locking @@ -2,10 +2,6 @@ JFFS2 LOCKING DOCUMENTATION --------------------------- -At least theoretically, JFFS2 does not require the Big Kernel Lock -(BKL), which was always helpfully obtained for it by Linux 2.4 VFS -code. It has its own locking, as described below. - This document attempts to describe the existing locking rules for JFFS2. It is not expected to remain perfectly up to date, but ought to be fairly close. @@ -69,6 +65,7 @@ Ordering constraints: any f->sem held. 2. Never attempt to lock two file mutexes in one thread. No ordering rules have been made for doing so. + 3. Never lock a page cache page with f->sem held. erase_completion_lock spinlock -- cgit v1.2.3-54-g00ecf