From: Kevin Corry <kcorry@austin.rr.com>
To: Greg KH <greg@kroah.com>, Mark Peloquin <peloquin@us.ibm.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
evms-devel@lists.sourceforge.net
Subject: Re: [PATCH] add safe version of list_for_each_entry() to list.h
Date: Thu, 3 Oct 2002 19:25:47 -0500 [thread overview]
Message-ID: <02100319254700.00236@cygnus> (raw)
In-Reply-To: <20021003234430.GG2289@kroah.com>
On Thursday 03 October 2002 18:44, Greg KH wrote:
> On Thu, Oct 03, 2002 at 06:42:09PM -0500, Mark Peloquin wrote:
> > Please consider adding the following patch to list.h.
>
> This patch had the tabs mangled and would not apply.
>
> Yeah, Notes sucks for sending patches...
It does indeed. Avoid Notes at all costs. :)
Here is the patch again. Should apply cleanly this time.
-Kevin
=========================================================
diff -Naur linux-2.5.40a/include/linux/list.h linux-2.5.40b/include/linux/list.h
--- linux-2.5.40a/include/linux/list.h Tue Oct 1 02:05:48 2002
+++ linux-2.5.40b/include/linux/list.h Thu Oct 3 19:17:27 2002
@@ -137,6 +137,15 @@
return head->next == head;
}
+/**
+ * list_member - tests whether a list member is currently on a list
+ * @member: member to evaulate
+ */
+static inline int list_member(struct list_head *member)
+{
+ return ((!member->next || !member->prev) ? 0 : 1);
+}
+
static inline void __list_splice(struct list_head *list,
struct list_head *head)
{
@@ -240,6 +249,20 @@
&pos->member != (head); \
pos = list_entry(pos->member.next, typeof(*pos), member), \
prefetch(pos->member.next))
+
+/**
+ * list_for_each_entry_safe - iterate over list safe against removal of list entry
+ * @pos: the type * to use as a loop counter.
+ * @n: another type * to use as temporary storage
+ * @head: the head for your list.
+ * @member: the name of the list_struct within the struct.
+ */
+#define list_for_each_entry_safe(pos, n, head, member) \
+ for (pos = list_entry((head)->next, typeof(*pos), member), \
+ n = list_entry(pos->member.next, typeof(*pos), member); \
+ &pos->member != (head); \
+ pos = n, \
+ n = list_entry(pos->member.next, typeof(*pos), member))
#endif /* __KERNEL__ || _LVM_H_INCLUDE */
next prev parent reply other threads:[~2002-10-04 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 23:42 [PATCH] add safe version of list_for_each_entry() to list.h Mark Peloquin
2002-10-03 23:44 ` Greg KH
2002-10-04 0:25 ` Kevin Corry [this message]
2002-10-04 13:58 ` Christoph Hellwig
2002-10-04 13:48 ` Kevin Corry
2002-10-04 13:51 ` Kevin Corry
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 15:05 Matthew Wilcox
2002-10-04 15:48 Mark Peloquin
2002-10-04 16:00 ` Matthew Wilcox
2002-10-04 16:33 ` Andrew Morton
2002-10-04 16:40 Mark Peloquin
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=02100319254700.00236@cygnus \
--to=kcorry@austin.rr.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peloquin@us.ibm.com \
--cc=torvalds@transmeta.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