mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] seqlock,lockdep: Add lock primitives to read_seqbegin().
Date: Tue, 29 Mar 2011 08:49:02 -0400	[thread overview]
Message-ID: <1301402942.14261.266.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <201103290430.p2T4UhLA081016@www262.sakura.ne.jp>

On Tue, 2011-03-29 at 13:30 +0900, Tetsuo Handa wrote:
> I made a small test module (which should work on 2.6.38.2).

Thanks! I'll take a look at this later today.
> 
> ---------- locktest.c start ----------
[...]
> ---------- Makefile end ----------
> 
> Below are my testcases and results (gcc 3.3 / x86_32).
> Kernel config is at http://I-love.SAKURA.ne.jp/tmp/config-2.6.38.2 .
> 
> ---------- Testcase 1 ----------
> 
> # cat /proc/locktest1
> # cat /proc/locktest2
> # cat /proc/locktest1
> # cat /proc/locktest2
> # cat /proc/locktest1
> # cat /proc/locktest2
> 
> showed nothing in dmesg.
> 
> ---------- Testcase 2 ----------
> 
> # cat /proc/locktest1
> # cat /proc/locktest2
> # cat /proc/locktest3
> 
> showed below message.
> 
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.38.2 #1
> -------------------------------------------------------

[...]

> Well... did I misuse spinlock primitives in read_seqbegin2()?
> Anyway, lockdep should catch testcase 1.

Strange. I'll investigate this further.

Thanks,

-- Steve



  reply	other threads:[~2011-03-29 12:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26  4:12 Tetsuo Handa
2011-03-28 17:12 ` Steven Rostedt
2011-03-28 21:57   ` Tetsuo Handa
2011-03-29  4:30   ` Tetsuo Handa
2011-03-29 12:49     ` Steven Rostedt [this message]
2011-03-29 13:39     ` Peter Zijlstra
2011-03-29 17:50       ` Peter Zijlstra
2011-03-30  8:12         ` Tetsuo Handa
2011-03-30  9:50           ` Peter Zijlstra
2011-03-30 12:17             ` Tetsuo Handa
2011-03-31 13:59               ` Peter Zijlstra
2011-03-29 13:11 ` Peter Zijlstra
2011-03-29 13:14 ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1301402942.14261.266.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®