linux-kernel - [PATCH 0/3] kill-the-BKL/reiserfs: reiserfs fixes

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1239680065-25013-1-git-send-email-fweisbec@gmail.com>
Date:	Tue, 14 Apr 2009 05:34:22 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Alessio Igor Bogani <abogani@...ware.it>,
	Jeff Mahoney <jeffm@...e.com>,
	ReiserFS Development List <reiserfs-devel@...r.kernel.org>,
	Alexander Beregalov <a.beregalov@...il.com>,
	Chris Mason <chris.mason@...cle.com>
Subject: [PATCH 0/3] kill-the-BKL/reiserfs: reiserfs fixes

Ingo,

This small patchset fixes some deadlocks I've faced after trying
some pressures with dbench on a reiserfs partition.

There is still some work pending such as adding some checks to ensure we
_always_ release the lock before sleeping, as you suggested.
Also I have to fix a lockdep warning reported by Alessio Igor Bogani.
And also some optimizations....

Thanks,
Frederic.

Frederic Weisbecker (3):
  kill-the-BKL/reiserfs: provide a tool to lock only once the write lock
  kill-the-BKL/reiserfs: lock only once in reiserfs_truncate_file
  kill-the-BKL/reiserfs: only acquire the write lock once in
    reiserfs_dirty_inode

 fs/reiserfs/inode.c         |   10 +++++++---
 fs/reiserfs/lock.c          |   26 ++++++++++++++++++++++++++
 fs/reiserfs/super.c         |   15 +++++++++------
 include/linux/reiserfs_fs.h |    2 ++
 4 files changed, 44 insertions(+), 9 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/