RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1283558 - tcsd fails to start if there is no tpm_* module in lsmod's output or insmod fails in loading tpm_* modules
Summary: tcsd fails to start if there is no tpm_* module in lsmod's output or insmod f...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: trousers
Version: 6.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jerry Snitselaar
QA Contact: Vilém Maršík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-19 09:53 UTC by Jaroslav Aster
Modified: 2017-12-06 11:36 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:36:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Aster 2015-11-19 09:53:37 UTC
Description of problem:

tcsd fails to start if there is no tpm_* module in lsmod's output or insmod fails in loading tpm_* modules. The issue is in the initscript in function start(). There is this code

check_drivers || load_drivers || exit 1

Function check_drivers() does lsmod and checks if there is tpm_* module in the output. This is wrong because tpm module can be built-in and in this case it will not be in lsmod's output. In my case, I use tpm-emulator. tpm-emulator does not have tpm_* module (It has tpmd_dev module), but it creates /dev/tpm device so trousers works as it's expected. This is not problem on x86_64/i386. There is tpm_infineon module which is always loaded not matter there is or is not tpm device on the system. The problem is only on ppc64 and s390x. 

The better way is to check existence of /dev/tpm instead of exitence of tpm_* kernel module, but it does tcsd itself.

There are no such limitations on rhel-7, so I suggest to remove check from the initscript.

Version-Release number of selected component (if applicable):

trousers-0.3.13-2.el6

How reproducible:

100%


Actual results:

tcsd does not start if there is no tpm_* module in the system.


Expected results:

tcsd start if there is /dev/tpm device.

Additional info:

Comment 2 Jan Kurik 2017-12-06 11:36:48 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


Note You need to log in before you can comment on or make changes to this bug.