linux-kernel - [PATCH 0/8] Fix assorted FS-Cache issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 03 May 2013 01:33:16 +0100
From:	David Howells <dhowells@...hat.com>
To:	linux-cachefs@...hat.com
Cc:	linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
	hjayasur@...hat.com, jlayton@...hat.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/8] Fix assorted FS-Cache issues



Following this mail is a series of patches to fix a number of FS-Cache issues,
including a number of oopses.  The patches can also be found at:

	http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache

The patches are as follows:

 (1) Don't put spin_lock() in a while-condition as spin_lock() may be wrapped
     with do {} while(0) (cleanup).

 (2) Name i_mutex lock classes rather than using numbers in CacheFiles (cleanup).

 (3) Don't sleep in page release if __GFP_FS is not set (deadlock vs ext4).

 (4) Uninline fscache_object_init() (cleanup).

 (5) Wrap checks on object state (cleanup).

 (6) Provide a system wait_on_atomic_t() and wake_up_atomic_t() (enhancement).

 (7) Simplify the object state machine (need #4 and #5).

 (8) Simplify cookie retention by objects (oops fix, need #6 and #7).

David
---
David Howells (6):
      FS-Cache: Don't sleep in page release if __GFP_FS is not set
      FS-Cache: Uninline fscache_object_init()
      FS-Cache: Wrap checks on object state
      Add wait_on_atomic_t() and wake_up_atomic_t()
      FS-Cache: Fix object state machine to have separate work and wait states
      FS-Cache: Simplify cookie retention for fscache_objects, fixing access problems

J. Bruce Fields (1):
      CacheFiles: name i_mutex lock class explicitly

Sebastian Andrzej Siewior (1):
      fs/fscache: remove spin_lock() from the condition in while()


 fs/cachefiles/interface.c     |   11 
 fs/cachefiles/namei.c         |   10 
 fs/cachefiles/xattr.c         |    6 
 fs/fscache/cache.c            |   34 +
 fs/fscache/cookie.c           |   93 +---
 fs/fscache/fsdef.c            |    1 
 fs/fscache/internal.h         |   11 
 fs/fscache/main.c             |   11 
 fs/fscache/netfs.c            |    1 
 fs/fscache/object-list.c      |  103 ++--
 fs/fscache/object.c           | 1077 +++++++++++++++++++++--------------------
 fs/fscache/operation.c        |   36 +
 fs/fscache/page.c             |   55 +-
 include/linux/fscache-cache.h |  170 +++---
 include/linux/wait.h          |   29 +
 kernel/wait.c                 |   85 +++
 16 files changed, 922 insertions(+), 811 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/