All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yubin Ruan <ablacktshirt@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Listing 9.2: actual free(3) will probably cause problem
Date: Sat, 28 Oct 2017 06:12:27 -0700	[thread overview]
Message-ID: <20171028131227.GV3659@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171028092932.GG5742@HP>

On Sat, Oct 28, 2017 at 05:29:34PM +0800, Yubin Ruan wrote:
> Hi Paul,
> 
> I would suggest the following patch for defer/route_refcnt.c (as in Listing
> 9.2). For the change in re_free, if we actually call free(3) on `rep', we will
> lose that piece of memory so that the READ_ONCE() at line 36 might see garbage
> value and will probably will not call abort(3), i.e., that is implementation
> specific behavior. And I don't see why will we have `old <=0`.
> 
> I think I understand what that code mean but you might mean some other?
> Hopefully I will not be too picky.

Yes, this code is buggy and fixing it is on my list.  I would be happy to
accept a patch doing a real fix, but it is not simple.

One place to start is Anthony Williams's atomic shared pointer code.
The idea would be to translate that from C++ to C.

But please be aware that this is a non-trivial problem.  If you try to
hack together a solution, it -will- have subtle bugs.  So validating
your solution (even if you start from Anthony's approach) will be
non-trivial.  I suggest using cbmc or something similar in addition to
perfbook's stress tests.

So, are you up for it?  ;-)

							Thanx, Paul

> Thanks,
> Yubin
> 
> ----------------------------------------
> diff --git a/CodeSamples/defer/route_refcnt.c b/CodeSamples/defer/route_refcnt.c
> index 8a48faf..0d24e9d 100644
> --- a/CodeSamples/defer/route_refcnt.c
> +++ b/CodeSamples/defer/route_refcnt.c
> @@ -36,7 +36,8 @@ DEFINE_SPINLOCK(routelock);
>  static void re_free(struct route_entry *rep)
>  {
>  	WRITE_ONCE(rep->re_freed, 1);
> -	free(rep);
> +    /* Will not actually free it. Just use the `re_freed' as a flag */
> +	/*free(rep);*/
>  }
> 
>  /*
> @@ -50,7 +51,6 @@ unsigned long route_lookup(unsigned long addr)
>  	struct route_entry **repp;
>  	unsigned long ret;
> 
> -retry:
>  	repp = &route_list.re_next;
>  	rep = NULL;
>  	do {
> @@ -65,8 +65,6 @@ retry:
>  			if (READ_ONCE(rep->re_freed))
>  				abort();
>  			old = atomic_read(&rep->re_refcnt);
> -			if (old <= 0)
> -				goto retry;
>  			new = old + 1;
>  		} while (atomic_cmpxchg(&rep->re_refcnt, old, new) != old);
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2017-10-28 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  9:29 Listing 9.2: actual free(3) will probably cause problem Yubin Ruan
2017-10-28 13:12 ` Paul E. McKenney [this message]
2017-10-29  1:19   ` Yubin Ruan
2017-10-29 11:42     ` Akira Yokosawa
2017-10-29 19:21       ` Paul E. McKenney

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=20171028131227.GV3659@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=ablacktshirt@gmail.com \
    --cc=perfbook@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.