From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
mingo@elte.hu, daniel.blueman@gmail.com, clameter@sgi.com,
torvalds@linux-foundation.org, rjw@sisk.pl,
linux-kernel@vger.kernel.org, bunk@kernel.org,
protasnb@gmail.com, kernel-testers@vger.kernel.org
Subject: Re: [PATCH] debugobjects: fix lockdep warning #2
Date: Fri, 29 Aug 2008 16:02:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0808291558470.3243@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080828171706.6080accf.akpm@linux-foundation.org>
On Thu, 28 Aug 2008, Andrew Morton wrote:
> >
> > The lock is also promoted to irq-safe (suggested by Dan).
>
> What was the reason for this other change? I'm sure Dan is a fine chap,
> but we usually prefer a little more justification for changes ;)
I added the info already, when I applied it to the tip-tree.
> > + /* Now free them */
> > + hlist_for_each_entry_safe(obj, node, tmp, &freelist, node) {
> > + hlist_del(&obj->node);
> > + free_object(obj);
>
> I suspect that we can avoid the hlist_del() here, perhaps with a little
> effort.
>
> > +
> > + /* Now free them */
> > + hlist_for_each_entry_safe(obj, node, tmp, &freelist, node) {
> > + hlist_del(&obj->node);
> > + free_object(obj);
> > + }
> > +
>
> and the other one.
>
> But I'm not sure that it's worth putting effort into - leaving dead
> objects strung onto a partially-live list is a little bit smelly IMO.
I really feel better, when we delete them instead of throwing them
away with pointers to each other.
Thanks,
tglx
next prev parent reply other threads:[~2008-08-29 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 15:32 Vegard Nossum
2008-08-29 0:17 ` Andrew Morton
2008-08-29 14:02 ` Thomas Gleixner [this message]
2008-08-29 21:57 ` Daniel J Blueman
2008-09-01 10:59 ` [GIT pull] debugobject fixes for 2.6.27 Thomas Gleixner
2008-08-29 10:42 ` [PATCH] debugobjects: fix lockdep warning #2 Thomas Gleixner
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=alpine.LFD.1.10.0808291558470.3243@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=clameter@sgi.com \
--cc=daniel.blueman@gmail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
/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®