mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Santiago Font Arquer" <sfa.linux@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: skb_clone SMP race?
Date: Wed, 10 Oct 2007 10:37:57 +0200	[thread overview]
Message-ID: <dfad5c650710100137i74f444d8t221f1f195cc90e1@mail.gmail.com> (raw)

Hello,
    I'm studying the implementation of sk_buff and I think there's a
possible race condition in skb_clone (2.6.22.9)
    The code is:


struct sk_buff *skb_clone(struct sk_buff *skb, gfp_t gfp_mask)
{
 struct sk_buff *n;

 n = skb + 1;
 if (skb->fclone == SKB_FCLONE_ORIG &&
     n->fclone == SKB_FCLONE_UNAVAILABLE) {
  atomic_t *fclone_ref = (atomic_t *) (n + 1);
  n->fclone = SKB_FCLONE_CLONE;
  atomic_inc(fclone_ref);
 } else {
  n = kmem_cache_alloc(skbuff_head_cache, gfp_mask);
  if (!n)
   return NULL;
  n->fclone = SKB_FCLONE_UNAVAILABLE;
 }

    If an skb with fast clone available (first "if" true) has
references in different CPUs (skb->users>1) (I do not find explicit
checks for this to be impossible), if skb_clone is called
simultaneously over that skb, both callers can get the same clone (the
"fast" clone) and different problems follow: wrong "clone_skb->users"
(1 as expected by the caller, but it should be, to be true, 2),
fclone_ref set to 3 involving further problems, ...

   IMO, the same problem arises although the calls to skb_clone are
not simultaneous: there isn´t a memory barrier after the change of
"n->fclone" to guarantee the visibility of that change to other CPUs
(but that barrier will not solve anything; I mentioned this only to
reflect another reason I see for the race to happen).

   Is that correct? Thank you in advance.

        Santiago Font Arquer

             reply	other threads:[~2007-10-10  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10  8:37 Santiago Font Arquer [this message]
2007-10-10  8:43 ` David Miller

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=dfad5c650710100137i74f444d8t221f1f195cc90e1@mail.gmail.com \
    --to=sfa.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®