mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	James Morris <jmoriss@namei.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Peter Dolding <oiaohm@gmail.com>,
	Kenneth Goldman <kgoldman@us.ibm.com>,
	Debora Velarde <debora@linux.vnet.ibm.com>,
	David Safford <safford@watson.ibm.com>,
	Serge Hallyn <serue@linux.vnet.ibm.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Pavel Machek <pavel@suse.cz>, Greg KH <greg@kroah.com>,
	Christoph Hellwig <hch@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Subject: [PATCH 0/2] TPM
Date: Sat, 30 Aug 2008 00:05:02 -0300	[thread overview]
Message-ID: <cover.1220065144.git.srajiv@linux.vnet.ibm.com> (raw)

Based on Christoph Hellwig's TPM internal kernel interface 
locking question, the following TPM changes were made: 
        - removal of the BKL calls from the TPM driver, which were
          added in the overall misc-char-dev-BKL-pushdown.patch
        - continue to protect the tpm_chip_list using the 
          driver_lock, and add an rcu to protect readers.

The TPM internal kernel interface patch will be posted as 
part of the integrity patchset.

 drivers/char/tpm/tpm.c |  285 +++++++++++++++++++++++++++++++-----------------
 drivers/char/tpm/tpm.h |    2 +-
 2 files changed, 188 insertions(+), 99 deletions(-)


             reply	other threads:[~2008-08-30  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30  3:05 Rajiv Andrade [this message]
2008-08-30  3:05 ` [PATCH 1/2] TPM: update char dev BKL pushdown Rajiv Andrade
2008-09-02 15:03   ` Serge E. Hallyn
2008-08-30  3:05 ` [PATCH 2/2] TPM: rcu locking Rajiv Andrade
2008-08-31 20:28   ` Paul E. McKenney
2008-09-02 15:19     ` Serge E. Hallyn
2008-09-11 18:16     ` Mimi Zohar

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=cover.1220065144.git.srajiv@linux.vnet.ibm.com \
    --to=srajiv@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=debora@linux.vnet.ibm.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=jmoriss@namei.org \
    --cc=kgoldman@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oiaohm@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pavel@suse.cz \
    --cc=safford@watson.ibm.com \
    --cc=serue@linux.vnet.ibm.com \
    --cc=zohar@linux.vnet.ibm.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

Powered by JetHome