Bug 234338 - use printk for error message before returning LM_OUT_ERROR
use printk for error message before returning LM_OUT_ERROR
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Teigland
Dean Jansa
Depends On:
  Show dependency treegraph
Reported: 2007-03-28 11:54 EDT by David Teigland
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2007-0959
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 14:45:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch posted to rhkernel on 04/19 (1.20 KB, text/plain)
2007-04-19 13:39 EDT, David Teigland
no flags Details

  None (edit)
Description David Teigland 2007-03-28 11:54:40 EDT
Description of problem:

In fs/gfs2/locking/dlm/lock.c, right before LM_OUT_ERROR is returned there's a
log_debug() -- that should _really_ have been a log_error() so we'd see it when
debugging was disabled.

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 RHEL Product and Program Management 2007-04-13 14:45:40 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 2 David Teigland 2007-04-19 13:39:49 EDT
Created attachment 153039 [details]
patch posted to rhkernel on 04/19
Comment 3 Don Zickus 2007-05-01 14:08:28 EDT
in 2.6.18-17.el5
Comment 6 errata-xmlrpc 2007-11-07 14:45:35 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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