From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: wrose@loislaw.com, linux-kernel@vger.kernel.org
Subject: Re: Segfault hidden in list.h
Date: Sun, 12 May 2002 19:08:57 -0700 (PDT) [thread overview]
Message-ID: <20020512.190857.07007452.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205121805220.15392-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Sun, 12 May 2002 18:08:28 -0700 (PDT)
And I'm sure as hell not going to put any lockless stuff in functions
meant for "normal human consumption". If we create list macros like that,
they had better be called "lockless_list_add_be_damn_careful_about_it()"
rather than "list_add()".
That was what I was suggesting. I didn't intend for the memory
barriers to go into the existing list macros.
next prev parent reply other threads:[~2002-05-13 2:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 0:37 Segfault hidden in list.h Rose, Billy
2002-05-13 0:59 ` Linus Torvalds
2002-05-13 0:50 ` David S. Miller
2002-05-13 1:08 ` Linus Torvalds
2002-05-13 2:08 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 1:02 Rose, Billy
2002-05-13 1:34 ` Davide Libenzi
2002-05-13 1:10 Rose, Billy
2002-05-13 2:17 Rose, Billy
2002-05-13 6:33 Dipankar Sarma
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=20020512.190857.07007452.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=wrose@loislaw.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