From: pravin b shelar <pravins@calsoftinc.com>
To: "Christoph Lameter"@calsoftinc.com, netdev@oss.sgi.com,
davem@davemloft.net
Subject: Re: Fwd: atomic_dec_and_test for child dst needed in dst_destroy?
Date: Wed, 06 Apr 2005 14:23:52 +0530 [thread overview]
Message-ID: <4253A3A0.800@calsoftinc.com> (raw)
In-Reply-To: <b82a8917050406002339f732ca@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
>
>
>This is racy (albeit very unlikely) because dst may be freed by
>dst_run_gc after the atomic_dec.
>
>When we are not the real parent of the dst (e.g., when we're xfrm_dst
>and the child is an rtentry), it may already be on the GC list.
>
>In fact the current code is buggy to, we need to check dst->flags
>before the dec as dst may no longer be valid afterwards.
>
>
>
>
This patch will remove the need for atomic_dec_and_test for this
particular case.
Now we can break down the atomic_dec_and_test to atomic_dec & atomic_read.
Please comment.
Regards
Pravin.
[-- Attachment #2: dst-atomic --]
[-- Type: text/plain, Size: 991 bytes --]
Index: linux-2.6.11-dsta/net/core/dst.c
===================================================================
--- linux-2.6.11-dsta.orig/net/core/dst.c 2005-04-06 00:18:32.000000000 -0700
+++ linux-2.6.11-dsta/net/core/dst.c 2005-04-06 01:31:10.000000000 -0700
@@ -198,17 +198,19 @@
dst = child;
if (dst) {
- if (atomic_dec_and_test(&dst->__refcnt)) {
- /* We were real parent of this dst, so kill child. */
- if (dst->flags&DST_NOHASH)
- goto again;
- } else {
- /* Child is still referenced, return it for freeing. */
- if (dst->flags&DST_NOHASH)
- return dst;
- /* Child is still in his hash table */
+ if (dst->flags&DST_NOHASH) {
+ atomic_dec(&dst->__refcnt);
+ if (atomic_read(&dst->__refcnt))
+ /* Child is still referenced, return it for freeing. */
+ return dst;
+
+ /*We were real parent of this dst, so kill child. */
+ goto again;
}
+ else /* Child is still in his hash table */
+ atomic_dec(&dst->__refcnt);
}
+
return NULL;
}
next prev parent reply other threads:[~2005-04-06 8:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 18:55 atomic_dec_and_test for child dst needed in dst_destroy? Christoph Lameter
2005-04-05 19:34 ` David S. Miller
2005-04-05 19:47 ` Christoph Lameter
2005-04-05 19:50 ` David S. Miller
2005-04-05 19:58 ` Christoph Lameter
2005-04-05 20:12 ` David S. Miller
2005-04-05 21:45 ` Herbert Xu
2005-04-05 21:48 ` David S. Miller
2005-04-05 22:14 ` Christoph Lameter
2005-04-06 2:19 ` Herbert Xu
2005-04-06 3:19 ` Christoph Lameter
2005-04-06 8:32 ` Herbert Xu
2005-04-06 18:17 ` David S. Miller
2005-04-06 18:48 ` Christoph Lameter
2005-04-07 11:07 ` Herbert Xu
2005-04-07 16:00 ` Christoph Lameter
2005-04-07 21:25 ` Herbert Xu
2005-04-07 22:30 ` Christoph Lameter
2005-04-07 23:07 ` Herbert Xu
2005-04-08 5:45 ` Christoph Lameter
2005-04-08 5:48 ` Herbert Xu
2005-04-08 15:05 ` Christoph Lameter
2005-04-08 21:45 ` Herbert Xu
2005-04-09 15:28 ` Christoph Lameter
[not found] ` <b82a8917050406002339f732ca@mail.gmail.com>
2005-04-06 8:53 ` pravin b shelar [this message]
2005-04-07 11:23 ` Fwd: " Herbert Xu
2005-04-07 12:30 ` pravin b shelar
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=4253A3A0.800@calsoftinc.com \
--to=pravins@calsoftinc.com \
--cc="Christoph Lameter"@calsoftinc.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).