From: Andrew Morton <akpm@zip.com.au>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2/16] list_head debugging
Date: Mon, 03 Jun 2002 13:16:49 -0700 [thread overview]
Message-ID: <3CFBCEB1.DFB6EF61@zip.com.au> (raw)
In-Reply-To: <3CF88863.BF3AF0FA@zip.com.au> <20020603135534.GA7668@ravel.coda.cs.cmu.edu>
Jan Harkes wrote:
>
> On Sat, Jun 01, 2002 at 01:40:03AM -0700, Andrew Morton wrote:
> > The patch nulls out the dangling pointers so we get a nice oops at the
> > site of the buggy code.
> ...
> > static __inline__ void list_del(struct list_head *entry)
> > {
> > __list_del(entry->prev, entry->next);
> > + /*
> > + * This is debug. Remove it when the kernel has no bugs ;)
> > + */
> > + entry->next = 0;
> > + entry->prev = 0;
> > }
>
> We've had this before, and it breaks some code that removes items from
> lists as follows,
>
> list_for_each(p, list)
> if (condition)
> list_del(p);
hmm. I suppose that's sane.
> These would have to either use __list_del, or need to do,
>
> for(p = list.next; p != &list;) {
> struct list_head *n = p->next;
> if (condition)
> list_del(p);
> p = n;
> }
list_for_each_safe() does this.
next prev parent reply other threads:[~2002-06-03 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 8:40 [patch 2/16] list_head debugging Andrew Morton
2002-06-01 17:19 ` Arnaldo Carvalho de Melo
2002-06-03 13:55 ` Jan Harkes
2002-06-03 20:16 ` Andrew Morton [this message]
2002-06-03 20:41 ` Rik van Riel
2002-06-10 16:36 ` Jan Harkes
2002-06-14 9:22 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 14:17 Bernd Jendrissek
2002-06-07 18:30 ` Andrew Morton
2002-06-07 18:30 ` Andrew Morton
2002-06-14 12:07 ` Jozsef Kadlecsik
2002-06-14 12:07 ` Jozsef Kadlecsik
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=3CFBCEB1.DFB6EF61@zip.com.au \
--to=akpm@zip.com.au \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.