From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 3/4] ptrlist: add MARK_CURRENT_DELETED
Date: Fri, 4 Aug 2017 22:09:14 +0200 [thread overview]
Message-ID: <20170804200915.56738-4-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170804200915.56738-1-luc.vanoostenryck@gmail.com>
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
ptrlist.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/ptrlist.h b/ptrlist.h
index d8203cf0b..74b80e220 100644
--- a/ptrlist.h
+++ b/ptrlist.h
@@ -287,6 +287,14 @@ extern void split_ptr_list_head(struct ptr_list *);
#define REPLACE_CURRENT_PTR(ptr, new_ptr) \
do { *THIS_ADDRESS(ptr) = (new_ptr); } while (0)
+#define DO_MARK_CURRENT_DELETED(ptr, __list) do { \
+ REPLACE_CURRENT_PTR(ptr, NULL); \
+ __list->rm++; \
+ } while (0)
+
+#define MARK_CURRENT_DELETED(ptr) \
+ DO_MARK_CURRENT_DELETED(ptr, __list##ptr)
+
extern void pack_ptr_list(struct ptr_list **);
#define PACK_PTR_LIST(x) pack_ptr_list((struct ptr_list **)(x))
--
2.13.2
next prev parent reply other threads:[~2017-08-04 20:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 15:32 [PATCH RFC] Let pseudo->users loop on duplicate version of list Christopher Li
2017-07-11 20:53 ` Christopher Li
2017-07-11 21:04 ` Dibyendu Majumdar
2017-07-12 5:29 ` Christopher Li
2017-07-12 15:56 ` Dibyendu Majumdar
2017-07-12 17:03 ` Christopher Li
2017-07-12 18:05 ` Dibyendu Majumdar
2017-07-13 5:27 ` Christopher Li
2017-07-19 21:14 ` Luc Van Oostenryck
2017-07-19 21:42 ` Christopher Li
2017-07-19 22:51 ` Luc Van Oostenryck
2017-07-20 2:34 ` Christopher Li
2017-08-02 23:44 ` Luc Van Oostenryck
2017-08-03 0:50 ` Christopher Li
2017-08-03 10:18 ` Luc Van Oostenryck
2017-08-03 23:48 ` Christopher Li
2017-08-04 0:41 ` Luc Van Oostenryck
2017-08-04 2:22 ` Christopher Li
2017-08-04 10:38 ` Luc Van Oostenryck
2017-08-04 14:48 ` Christopher Li
2017-08-04 16:58 ` Luc Van Oostenryck
[not found] ` <20170804002230.5047-1-luc.vanoostenryck@gmail.com>
2017-08-04 14:54 ` Fwd: [PATCH] mark pseudo user as deleted instead of removing them Christopher Li
2017-08-04 15:29 ` Christopher Li
2017-08-04 15:58 ` Luc Van Oostenryck
2017-08-04 18:19 ` Christopher Li
2017-08-04 19:12 ` Luc Van Oostenryck
2017-08-04 19:24 ` Christopher Li
2017-08-04 20:09 ` [PATCH 0/4] fix list corruption with recursive remove_usage() Luc Van Oostenryck
2017-08-04 20:09 ` [PATCH 1/4] ptrlist: add a counter for the number of removed elemnets Luc Van Oostenryck
2017-08-04 20:09 ` [PATCH 2/4] ptrlist: adjust ptr_list_size for the new ->rm field Luc Van Oostenryck
2017-08-04 20:09 ` Luc Van Oostenryck [this message]
2017-08-04 20:09 ` [PATCH 4/4] mark pseudo users as deleted instead of removing them Luc Van Oostenryck
2017-08-04 20:17 ` Christopher Li
2017-08-04 20:18 ` Christopher Li
2017-08-04 20:34 ` Luc Van Oostenryck
2017-08-04 20:48 ` Christopher Li
2017-08-04 21:03 ` Luc Van Oostenryck
2017-08-04 21:14 ` Christopher Li
2017-08-04 21:34 ` Luc Van Oostenryck
2017-08-04 16:54 ` [PATCH] mark pseudo user " Linus Torvalds
2017-08-04 18:33 ` Christopher Li
2017-08-04 20:08 ` Christopher Li
2017-08-04 20:37 ` Christopher Li
2017-07-13 12:23 ` [PATCH RFC] Let pseudo->users loop on duplicate version of list Christopher Li
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=20170804200915.56738-4-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).