From: Jochen Hein <jochen@jochen.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: kjhall@us.ibm.com, tpmdd-devel@lists.sourceforge.net
Subject: [TPM] broken /proc/misc entry
Date: Thu, 23 Jun 2005 20:41:57 +0200 [thread overview]
Message-ID: <874qboj4p6.fsf@echidna.jochen.org> (raw)
On my system I do have configured:
root@hermes:/dev# grep TPM /usr/src/linux-2.6.12/.config
# TPM devices
CONFIG_TCG_TPM=m
TPM is loaded:
root@hermes:/dev# lsmod | grep tpm
tpm_nsc 6272 0
tpm_atmel 4992 0
tpm 10496 2 tpm_nsc,tpm_atmel
/proc/misc contains:
root@hermes:/dev# cat /proc/misc
224
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ!
63 device-mapper
200 tun
1 psaux
175 agpgart
130 watchdog
144 nvram
135 rtc
After I removed the TPM modules I get:
root@hermes:/dev# rmmod tpm_nsc
root@hermes:/dev# rmmod tpm_atmel
root@hermes:/dev# rmmod tpm
root@hermes:/dev# cat /proc/misc
63 device-mapper
200 tun
1 psaux
175 agpgart
130 watchdog
144 nvram
135 rtc
Why on earth do we need to obfuscate the loaded TPM modules and the
misc minor number in that way? ls -l /dev/tpm gave that away easily.
>From the source:
if (misc_register(&chip->vendor->miscdev)) {
dev_err(&chip->pci_dev->dev,
"unable to misc_register %s, minor %d\n",
chip->vendor->miscdev.name,
chip->vendor->miscdev.minor);
pci_dev_put(pci_dev);
kfree(chip);
dev_mask[i] &= !(1 << j);
return -ENODEV;
}
Maybe it's a bad idea to use &chip->vendor->miscdev for registering
the misc device?
Jochen
--
#include <~/.signature>: permission denied
reply other threads:[~2005-06-23 18:52 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=874qboj4p6.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--cc=kjhall@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®