Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 313389 Details for
Bug 457779
possible recursive locking detected: (&inode->i_data.i_mmap_lock)
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
please test this patch
z (text/plain), 1.55 KB, created by
CPUShare
on 2008-08-04 18:02:03 UTC
(
hide
)
Description:
please test this patch
Filename:
MIME Type:
Creator:
CPUShare
Created:
2008-08-04 18:02:03 UTC
Size:
1.55 KB
patch
obsolete
>From: Andrea Arcangeli <andrea@qumranet.com> > >Lockdep can't recognize if spinlocks are at a different address. So >using trylock in a loop is one way to avoid lockdep to generate false >positives. After lockdep will be fixed this change can and should be >reverted. > >Signed-off-by: Andrea Arcangeli <andrea@qumranet.com> >--- > >Resubmit because I didn't update the subject and so I improved the >comments too. This is mostly to show it's a bug in lockdep and it can >be trivially worked around without having to fix lockdep for real, any >superior solution to this hack is more than welcome and recommended. > >diff -r 3469dce61df1 mm/mmap.c >--- a/mm/mmap.c Tue Jul 29 20:01:28 2008 +0200 >+++ b/mm/mmap.c Mon Aug 04 19:54:27 2008 +0200 >@@ -2279,8 +2279,12 @@ static void vm_lock_anon_vma(struct anon > /* > * The LSB of head.next can't change from under us > * because we hold the mm_all_locks_mutex. >+ * >+ * spin_lock would confuse lockdep who doesn't notice >+ * the 'anon_vma' always changing address. > */ >- spin_lock(&anon_vma->lock); >+ while (!spin_trylock(&anon_vma->lock)) >+ cpu_relax(); > /* > * We can safely modify head.next after taking the > * anon_vma->lock. If some other vma in this mm shares >@@ -2310,7 +2314,12 @@ static void vm_lock_mapping(struct addre > */ > if (test_and_set_bit(AS_MM_ALL_LOCKS, &mapping->flags)) > BUG(); >- spin_lock(&mapping->i_mmap_lock); >+ /* >+ * spin_lock would confuse lockdep who doesn't notice >+ * the 'mapping' always changing address. >+ */ >+ while (!spin_trylock(&mapping->i_mmap_lock)) >+ cpu_relax(); > } > } > >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 457779
: 313389