From: Kent Yoder <key@linux.vnet.ibm.com>
To: "Wei, Gang" <gang.wei@intel.com>
Cc: Kent Yoder <key@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"james.l.morris@oracle.com" <james.l.morris@oracle.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"ben@guthro.net" <ben@guthro.net>
Subject: Re: [PATCH] driver/char/tpm: fix regression causesd by ppi
Date: Wed, 10 Oct 2012 08:22:27 -0500 [thread overview]
Message-ID: <20121010132227.GB17467@ennui.austin.ibm.com> (raw)
In-Reply-To: <D0B11485C64D4B47B66902F8A4E901BE34FF5B@SHSMSX101.ccr.corp.intel.com>
> > Hmm, tpm_add_ppi is just sysfs_create_group, which only ever returns
> > 0. Looks like we can remove this error path, but PPI is unusable in the
> > failure case.
>
> sysfs_create_group will return 0 on success or return error code. So I don't
> think we can remove this error path. The previous call to sysfs_create_group
> also have similar error path.
Heh, seems "Returns 0 on success or error." doesn't mean what I
thought...
> >> +EXPORT_SYMBOL_GPL(tpm_add_ppi);
> >> ...
> >> +EXPORT_SYMBOL_GPL(tpm_remove_ppi);
> >>
> > Do we need to export these symbols? These might have been left around
> > from when ppi was a standalone module.
>
> We definitely need to export these symbols, since ppi was in tpm_bios.ko,
> and these symbols are called from tpm.ko.
Yes, thanks.
Kent
> Jimmy
prev parent reply other threads:[~2012-10-10 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 9:35 gang.wei
2012-10-09 22:18 ` Kent Yoder
2012-10-10 2:09 ` Wei, Gang
2012-10-10 13:22 ` Kent Yoder [this message]
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=20121010132227.GB17467@ennui.austin.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=ben@guthro.net \
--cc=ebiederm@xmission.com \
--cc=gang.wei@intel.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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®