Bug 445875 - implement rt_downgrade_write
implement rt_downgrade_write
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Steven Rostedt
Depends On:
  Show dependency treegraph
Reported: 2008-05-09 11:32 EDT by Clark Williams
Modified: 2009-07-07 09:36 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-07 09:36:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to workaround lack of rt_downgrade_write (2.21 KB, patch)
2008-05-09 15:37 EDT, Clark Williams
no flags Details | Diff
patch to implement downgrade write (4.76 KB, patch)
2008-05-21 10:33 EDT, Steven Rostedt
no flags Details | Diff

  None (edit)
Description Clark Williams 2008-05-09 11:32:16 EDT
Description of problem:
We're currently working around the act of downgrading a write lock into a read
lock due to the complexity of the implementation (updating data structures with
reference counts). After GA, need to revisit and implement rather than working

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

How reproducible:
LTP tests make use of sys_remap_file_pages() which triggers this

Steps to Reproduce:
1. login to test machine with LTP installed
2. as root start LTP test with 'runltp' script
3. look for traceback on console
Actual results:
WARNING: at kernel/rtmutex.c:1687 rt_read_fastunlock()
Pid: 7370, comm: remap_file_page Not tainted #1

Call Trace:
 [<ffffffff8105ee4f>] rt_mutex_up_read+0x36/0x201
 [<ffffffff8105f8c9>] rt_up_read+0x9/0xb
 [<ffffffff81091f21>] sys_remap_file_pages+0x359/0x38c
 [<ffffffff8100c31e>] tracesys+0xdc/0xe1

WARNING: at kernel/rtmutex.c:1688 rt_read_fastunlock()
Pid: 7370, comm: remap_file_page Not tainted #1

Call Trace:
 [<ffffffff8105ee7b>] rt_mutex_up_read+0x62/0x201
 [<ffffffff8105f8c9>] rt_up_read+0x9/0xb
 [<ffffffff81091f21>] sys_remap_file_pages+0x359/0x38c
 [<ffffffff8100c31e>] tracesys+0xdc/0xe1

Expected results:
no traceback on console
Comment 1 Clark Williams 2008-05-09 15:37:49 EDT
Created attachment 304981 [details]
Patch to workaround lack of rt_downgrade_write

This patch is a workaround to deal with the lack of a true downgrade mechanism
for write-locks.
Comment 2 Steven Rostedt 2008-05-21 10:33:54 EDT
Created attachment 306254 [details]
patch to implement downgrade write

This patch implements the downgrade write. It is a bit complex and not trivial
so I would suggest keeping the work around (avoiding the call to

I will continue to run rwlock torture tests to test all this code. When I am
satisfied with the results, I will notify Clark to remove the work around.

This BZ should remain open until that time. (otherwise I might forget ;-)
Comment 3 Clark Williams 2008-07-02 10:41:58 EDT
pulling downgrade workaround in upcoming -70 kernel build for testing
Comment 4 Luis Claudio R. Goncalves 2009-07-07 09:36:26 EDT
Fixed a long time ago...

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