Re: [PATCH tip/core/rcu 0/4] RCU debug-objects improvements

From: Sedat Dilek
Date: Tue Apr 23 2013 - 21:45:28 EST

Next message: wins: "The first $5,000.00 was sent today. My working partner has helped me to send the first $5,000.00 to you through western union. So contact our Western Union claims Agent to pick up this $5,000 now: Contact person: Mr. Ben Collins mail : (mrbencollins001@msn.com) Ask him to give you the MTCN, Sender Name to pick the $5,000.00. I told him to keep sending you $5,000.00 daily until the payment of $1.500,000.00 is completed. Again forward him your Full Name, Telephone number and address so that he will be sure.â"
Previous message: Minchan Kim: "[PATCH v2 3/6] mm: Remove shrink_page"
In reply to: Paul E. McKenney: "[PATCH tip/core/rcu 3/4] rcu: Make call_rcu() leak callbacks for debug-object errors"
Next in thread: Paul E. McKenney: "Re: [PATCH tip/core/rcu 0/4] RCU debug-objects improvements"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ QUOTE ]

Hello!

RCU's current debug-objects fixups are complex and heavyweight, plus the
fixups are not complete, because even with the fixups, RCU's callback
lists can still be corrupted. This series reworks RCU's use of the
debug-objects facility and the facility itself to allow improved handling
of things like duplicate invocations of call_rcu(). This series includes:

1. Simplify RCU's debug-objects fixups.

2. Make debug_object_activate() return status.

3. Make __call_rcu() leak callbacks when debug_object_activate()
notes suspicious activity. Leaking has its problems, but it
is far better than silent corruption of RCU's data structures.

4. Add a new object_debug option to rcutorture to allow
deterministic testing of #3 above.

Thanx, Paul

b/include/linux/debugobjects.h | 6 +-
b/kernel/rcu.h | 10 ++--
b/kernel/rcupdate.c | 100 -----------------------------------------
b/kernel/rcutorture.c | 37 +++++++++++++++
b/kernel/rcutree.c | 14 +++++
b/lib/debugobjects.c | 20 +++++---
6 files changed, 74 insertions(+), 113 deletions(-)

[ /QUOTE ]

I applied your patchset against the "buggy" Linux-Next (next-20130423)
with none of the ipc-sem-next patches (even w/o the suggested Linus
patch) to see if I see more debug-outputs,

I have attached my syslog while building my kernel.
Please, have a look!

Thanks for the patches.

Feel free to add to all of the 4 patches my Tested-by.

- Sedat -

[1] http://marc.info/?l=linux-kernel&m=136676361101735&w=2

Attachment: syslog.txt.gz
Description: GNU Zip compressed data

Attachment: syslog.txt.gz.sha256sum
Description: Binary data