From: Anton Blanchard <anton@samba.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Olaf Kirch <okir@suse.de>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arp_queue: serializing unlink + kfree_skb
Date: Fri, 4 Feb 2005 01:27:05 +1100 [thread overview]
Message-ID: <20050203142705.GA11318@krispykreme.ozlabs.ibm.com> (raw)
In-Reply-To: <E1CvZo6-0001Bz-00@gondolin.me.apana.org.au>
Hi,
> For example, in this particular case, a more sinister (but probably
> impossible for sk_buff objects) problem would be for the list removal
> itself to be delayed until after the the kfree_skb. This could
> potentially mean that we're reading/writing memory that's already
> been freed.
>
> Perhaps we should always add a barrier to such operations. So
> kfree_skb would become
>
> if (atomic_read(&skb->users) != 1) {
> smp_mb__before_atomic_dec();
> if (!atomic_dec_and_test(&skb->users))
> return;
> }
> __kfree_skb(skb);
Architectures should guarantee that any of the atomics and bitops that
return values order in both directions. So you dont need the
smp_mb__before_atomic_dec here.
It is, however, required on the atomics and bitops that dont return
values. Its difficult stuff, everyone gets it wrong and Andrew keeps
hassling me to write up a document explaining it.
Anton
next prev parent reply other threads:[~2005-02-03 14:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050131102920.GC4170@suse.de>
2005-01-31 11:33 ` Herbert Xu
2005-02-03 0:20 ` David S. Miller
2005-02-03 11:12 ` Herbert Xu
2005-02-04 0:34 ` David S. Miller
2005-02-03 14:27 ` Anton Blanchard [this message]
2005-02-03 18:14 ` David S. Miller
2005-02-03 20:30 ` Herbert Xu
2005-02-03 22:19 ` David S. Miller
2005-02-03 23:50 ` Herbert Xu
2005-02-04 0:49 ` David S. Miller
2005-02-04 1:20 ` Herbert Xu
2005-02-04 1:23 ` David S. Miller
2005-02-04 1:55 ` Herbert Xu
2005-02-04 11:16 ` Olaf Kirch
2005-02-06 1:14 ` David S. Miller
2005-02-03 23:08 ` David S. Miller
2005-02-04 11:33 ` Herbert Xu
2005-02-04 23:48 ` David S. Miller
2005-02-05 6:24 ` David S. Miller
2005-02-05 6:50 ` Herbert Xu
2005-02-10 4:23 ` Werner Almesberger
2005-02-10 4:56 ` Herbert Xu
2005-02-11 3:46 ` David S. Miller
2005-02-11 3:50 ` David S. Miller
2005-02-11 4:27 ` Werner Almesberger
2005-02-11 5:04 ` Dmitry Torokhov
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=20050203142705.GA11318@krispykreme.ozlabs.ibm.com \
--to=anton@samba.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=okir@suse.de \
/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®