mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	a.p.zijlstra@chello.nl, tglx@linutronix.de,
	viro@zeniv.linux.org.uk, kosaki.motohiro@jp.fujitsu.com,
	benh@kernel.crashing.org, paulus@samba.org, sparse@chrisli.org
Subject: Re: [GIT PULL] rcu: finalize debugobjects, first round of RCU sparse pointer checks
Date: Tue, 8 Jun 2010 20:07:01 +0200	[thread overview]
Message-ID: <20100608180701.GJ11585@elte.hu> (raw)
In-Reply-To: <20100601165034.GA9522@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> Here are the final commits from Mathieu's debugobjects series and the
> first few from Arnd's RCU-pointer sparse series.  The first three remove
> RCU's (useless) initializations from mm, fs, and powerpc:
> 
> mm:	http://lkml.org/lkml/2010/5/18/562
> fs:	http://lkml.org/lkml/2010/5/18/500
> powerpc:http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg43510.html
> 
> Kosaki Motohiro agreed that the mm patch should go up -tip, and none of
> the other maintainers objected to the prospect of their patches going
> up -tip.
> 
> The fourth patch removes RCU's initialization definitions, and the final
> four patches provide the beginnings of Arnd's RCU-pointer sparse checks.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
> 
> Or, if you prefer this against 2.6.34-rc7 without a merge record:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next-rc7
> 
> If you would rather me rebase this stack against 2.6.35-rc1, let me know!

I pulled the rcu/next-rc7 variant, thanks Paul!

New features are best done against stable kernels - i.e. v2.6.34. -rc7 was 
pretty stable too so it was fine to pull. .35-rc1 OTOH is something definitely 
more regression-prone than .34-rc7.

Except, of course, when we want to change code that is only in .35-rc1 - in 
that case merging to .35-rc1 (or later -rc's) is perfectly fine.

> Either way, once these commits reach mainline, I will submit the next 21
> commits to their respective trees.  The maintainers have been CCed on the
> earlier LKML patchsets (http://lkml.org/lkml/2010/5/12/372).  Once these
> 21 commits hit mainline, I will send you a pull request for the remaining
> two commits.
> 
> Then on to CONFIG_TINY_PREEMPT_RCU.
> 
> 							Thanx, Paul
> 
> ------------------>
>  Mathieu Desnoyers (2)
> 	 rcu head remove init
> 	 tree/tiny rcu: Add debug RCU head objects
> 
>  Paul E. McKenney (6)
> 	 powerpc: remove all rcu head initializations
> 	 fs: remove all rcu head initializations, except on_stack initializations
> 	 mm: remove all rcu head initializations
> 	 rcu: add an rcu_dereference_index_check()
> 	 rcu: add __rcu API for later sparse checking
> 	 lockdep: Add an in_workqueue_context() lockdep-based test function
> 
> 
>  arch/powerpc/mm/pgtable.c |    1 
>  fs/file.c                 |    3 
>  fs/fs-writeback.c         |   31 +++++++-
>  fs/partitions/check.c     |    1 
>  include/linux/compiler.h  |    2 
>  include/linux/rcupdate.h  |   88 ++++++++++++++++++++++-
>  include/linux/workqueue.h |    4 +
>  kernel/rcupdate.c         |  170 ++++++++++++++++++++++++++++++++++++++++++++++
>  kernel/rcutiny.c          |    2 
>  kernel/rcutree.c          |    2 
>  kernel/workqueue.c        |   15 ++++
>  lib/Kconfig.debug         |    6 +
>  mm/backing-dev.c          |    1 
>  mm/slob.c                 |    1 
>  14 files changed, 309 insertions(+), 18 deletions(-)

Thanks Paul!

	Ingo

  parent reply	other threads:[~2010-06-08 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 16:50 Paul E. McKenney
2010-06-02 10:34 ` KOSAKI Motohiro
2010-06-02 15:52   ` Andrew Morton
2010-06-03  3:58     ` KOSAKI Motohiro
2010-06-08 18:07 ` Ingo Molnar [this message]
2010-06-08 18:37   ` Ingo Molnar
2010-06-08 18:51     ` Paul E. McKenney
2010-06-08 19:07       ` Ingo Molnar

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=20100608180701.GJ11585@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=sparse@chrisli.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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®