linux-kernel - [RFC][PATCH 0/3] Coda: remove BKL

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]

Message-Id: <1287606184-26889-1-git-send-email-jaharkes@cs.cmu.edu>
Date:	Wed, 20 Oct 2010 16:23:01 -0400
From:	Jan Harkes <jaharkes@...cmu.edu>
To:	linux-fsdevel@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, arnd@...db.de
Subject: [RFC][PATCH 0/3] Coda: remove BKL

The following three patches remove the big kernel lock from the Coda
file system kernel module. We initially add a spinlock to protect the
Coda-specific inode data. After this we can push the BKL all the way
down to where the requests are queued for the userspace Coda cache
manager process and finally we replace the remaining BKL uses with a
mutex that protects the upcall queues.

Yoshihisa Abe (3):
      Coda: add spin lock to protect accesses to struct coda_inode_info.
      Coda: push BKL regions into coda_upcall()
      Coda: replace BKL with mutex

 fs/coda/cache.c            |   17 ++++--
 fs/coda/cnode.c            |   19 ++++--
 fs/coda/dir.c              |  158 ++++++++++++++------------------------------
 fs/coda/file.c             |   31 ++++-----
 fs/coda/inode.c            |   57 +++++++++-------
 fs/coda/pioctl.c           |   22 ++-----
 fs/coda/psdev.c            |   30 +++++----
 fs/coda/symlink.c          |    3 -
 fs/coda/upcall.c           |   24 +++++--
 include/linux/coda_fs_i.h  |   13 +++-
 include/linux/coda_linux.h |    6 ++-
 include/linux/coda_psdev.h |    2 +
 12 files changed, 177 insertions(+), 205 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/