From: David Teigland <teigland@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dlm fix for 2.6.29-rc1
Date: Mon, 12 Jan 2009 13:22:34 -0600 [thread overview]
Message-ID: <20090112192234.GB12875@redhat.com> (raw)
Linus,
Please pull two dlm patches for 2.6.29-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/dlm.git for-linus
The first fixes incorrect seq_file usage in the debugfs lock dump. I had
to rework all the seq ops which created the large diff.
The second isn't a fix, but changes an rwlock (used prominently in the
first patch) into a spinlock.
Thanks,
Dave
David Teigland (2):
dlm: fix seq_file usage in debugfs lock dump
dlm: change rsbtbl rwlock to spinlock
fs/dlm/debug_fs.c | 696 ++++++++++++++++++++++++-------------------------
fs/dlm/dlm_internal.h | 2 +-
fs/dlm/lock.c | 26 +-
fs/dlm/lockspace.c | 2 +-
fs/dlm/recover.c | 10 +-
5 files changed, 357 insertions(+), 379 deletions(-)
reply other threads:[~2009-01-12 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090112192234.GB12875@redhat.com \
--to=teigland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome