From: Byungchul Park <byungchul.park@lge.com>
To: peterz@infradead.org, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de,
sergey.senozhatsky@gmail.com, gregkh@linuxfoundation.org,
minchan@kernel.org
Subject: [PATCH 0/5] Implement bitlock map allocator
Date: Mon, 20 Jun 2016 13:55:10 +0900 [thread overview]
Message-ID: <1466398515-1005-1-git-send-email-byungchul.park@lge.com> (raw)
Currently, bit-based lock e.g. bit_spin_lock cannot use the lock
correctness validator using lockdep. However, it would be useful if
the validator supports for even bit-based lock as well.
Therefore, this patch provides interface for allocation and freeing
lockdep_map for bit-based lock so that the bit-based lock can also use
the lock correctness validator with the lockdep_map, allocated for each
bit address.
This patch can be applied to any bit_spin_lock user except slab
allocator where I am not sure if using kmalloc is safe. Anyway I chose
two example to apply bitlock map allocator, zram and buffer head.
And applied it and included it in this patch set.
Byungchul Park (5):
lockdep: Implement bitlock map allocator
lockdep: Apply bitlock to bit_spin_lock
lockdep: Apply bit_spin_lock lockdep to zram
fs/buffer.c: Remove trailing white space
lockdep: Apply bit_spin_lock lockdep to BH_Uptodate_Lock
drivers/block/zram/zram_drv.c | 10 +++
fs/buffer.c | 24 +++----
include/linux/bit_spinlock.h | 57 ++++++++++++++--
include/linux/bitlock.h | 20 ++++++
kernel/locking/Makefile | 1 +
kernel/locking/bitlock_map.c | 147 ++++++++++++++++++++++++++++++++++++++++++
lib/Kconfig.debug | 10 +++
7 files changed, 252 insertions(+), 17 deletions(-)
create mode 100644 include/linux/bitlock.h
create mode 100644 kernel/locking/bitlock_map.c
--
1.9.1
next reply other threads:[~2016-06-20 5:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 4:55 Byungchul Park [this message]
2016-06-20 4:55 ` [PATCH 1/5] lockdep: Implement bitlock map allocator Byungchul Park
2016-06-30 12:59 ` Peter Zijlstra
2016-07-01 0:24 ` Byungchul Park
2016-07-01 7:53 ` Peter Zijlstra
2016-07-04 7:29 ` Byungchul Park
2016-07-07 10:22 ` Byungchul Park
2016-07-13 20:17 ` Peter Zijlstra
2016-07-18 1:46 ` Byungchul Park
2016-06-20 4:55 ` [PATCH 2/5] lockdep: Apply bitlock to bit_spin_lock Byungchul Park
2016-06-20 4:55 ` [PATCH 3/5] lockdep: Apply bit_spin_lock lockdep to zram Byungchul Park
2016-06-20 15:36 ` Sergey Senozhatsky
2016-06-21 1:05 ` Byungchul Park
2016-06-20 4:55 ` [PATCH 4/5] fs/buffer.c: Remove trailing white space Byungchul Park
2016-06-20 4:55 ` [PATCH 5/5] lockdep: Apply bit_spin_lock lockdep to BH_Uptodate_Lock Byungchul Park
2016-06-29 12:45 ` [PATCH 0/5] Implement bitlock map allocator Byungchul Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1466398515-1005-1-git-send-email-byungchul.park@lge.com \
--to=byungchul.park@lge.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).