From: Chuck Ebbert <76306.1226@compuserve.com>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Willy Tarreau <w@1wt.eu>
Subject: Re: memory corruptor in .18rc1-git
Date: Sat, 15 Jul 2006 15:54:35 -0400 [thread overview]
Message-ID: <200607151556_MC3-1-C510-CFA2@compuserve.com> (raw)
In-Reply-To: <20060714043112.GA20478@redhat.com>
On Fri, 14 Jul 2006 00:31:12 -0400, Dave Jones wrote:
> +/**
> + * list_add - add a new entry
> + * @new: new entry to be added
> + * @head: list head to add it after
> + *
> + * Insert a new entry after the specified head.
> + * This is good for implementing stacks.
> + */
> +void list_add(struct list_head *new, struct list_head *head)
> +{
> + if (head->next->prev != head) {
> + printk("List corruption. next->prev should be %p, but was %p\n",
> + head, head->next->prev);
> + BUG();
> + }
> + if (head->prev->next != head) {
> + printk("List corruption. prev->next should be %p, but was %p\n",
> + head, head->prev->next);
> + BUG();
> + }
> +
> + __list_add(new, head, head->next);
> +}
> +EXPORT_SYMBOL(list_add);
> +
> +/**
> + * list_del - deletes entry from list.
> + * @entry: the element to delete from the list.
> + * Note: list_empty on entry does not return true after this, the entry is
> + * in an undefined state.
> + */
> +void list_del(struct list_head *entry)
> +{
> + if (entry->prev->next != entry) {
> + printk("List corruption. prev->next should be %p, but was %p\n",
> + entry, entry->prev->next);
> + BUG();
> + }
> + if (entry->next->prev != entry) {
> + printk("List corruption. next->prev should be %p, but was %p\n",
> + entry, entry->next->prev);
> + BUG();
> + }
> + __list_del(entry->prev, entry->next);
> + entry->next = LIST_POISON1;
> + entry->prev = LIST_POISON2;
> +}
> +EXPORT_SYMBOL(list_del);
> +
>
Shouldn't those four 'if' statements use unlikely()? There's no sense
causing more slowdown than necessary, even in debug code.
And I'd change the messages slightly, e.g.:
"list_add: corruption: next->prev should be %p, was %p\n"
Some people build (accidentally?) without verbose debug info and
don't get line numbers.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-07-15 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 19:54 Chuck Ebbert [this message]
2006-07-15 20:04 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 22:13 Dave Jones
2006-07-13 22:24 ` Andrew Morton
2006-07-13 22:30 ` Dave Jones
2006-07-14 4:12 ` Willy Tarreau
2006-07-14 4:20 ` Dave Jones
2006-07-14 4:25 ` Willy Tarreau
2006-07-14 4:31 ` Dave Jones
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=200607151556_MC3-1-C510-CFA2@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=w@1wt.eu \
/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®