mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, linux-kernel@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>,
	stable@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH RFC] ptr_ring: fix race conditions when resizing
Date: Mon, 13 Feb 2017 13:04:32 +0800	[thread overview]
Message-ID: <0aa7f7fc-3c10-2927-15d6-b061ea1add1f@redhat.com> (raw)
In-Reply-To: <1486765845-26587-1-git-send-email-mst@redhat.com>



On 2017年02月11日 06:31, Michael S. Tsirkin wrote:
> Resizing currently drops consumer lock.  This can cause entries to be
> reordered, which isn't good in itself.  More importantly, consumer can
> detect a false ring empty condition and block forever.
>
> Further, nesting of consumer within producer lock is problematic for
> tun, since it produces entries in an interrupt, which causes a

In an bh actually?

Except for this.

Acked-by: Jason Wang <jasowang@redhat.com>

> lock order reversal:
>
>         CPU0                    CPU1
>         ----                    ----
>    consume:
>    lock(&(&r->consumer_lock)->rlock);
>                                 resize:
>                                 local_irq_disable();
>                                 lock(&(&r->producer_lock)->rlock);
>                                 lock(&(&r->consumer_lock)->rlock);
>    <Interrupt>
>    produce:
>    lock(&(&r->producer_lock)->rlock);
>
> To fix, nest producer lock within consumer lock during resize,
> and keep consumer lock during the whole swap operation.
>
> Reported-by: Dmitry Vyukov <dvyukov@google.com>
> Cc: stable@vger.kernel.org
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>   include/linux/ptr_ring.h | 36 +++++++++++++++++++++++++++++++-----
>   1 file changed, 31 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/ptr_ring.h b/include/linux/ptr_ring.h
> index 2052011..6c70444 100644
> --- a/include/linux/ptr_ring.h
> +++ b/include/linux/ptr_ring.h
> @@ -111,6 +111,11 @@ static inline int __ptr_ring_produce(struct ptr_ring *r, void *ptr)
>   	return 0;
>   }
>   
> +/*
> + * Note: resize (below) nests producer lock within consumer lock, so if you
> + * consume in interrupt or BH context, you must disable interrupts/BH when
> + * calling this.
> + */
>   static inline int ptr_ring_produce(struct ptr_ring *r, void *ptr)
>   {
>   	int ret;
> @@ -242,6 +247,11 @@ static inline void *__ptr_ring_consume(struct ptr_ring *r)
>   	return ptr;
>   }
>   
> +/*
> + * Note: resize (below) nests producer lock within consumer lock, so if you
> + * call this in interrupt or BH context, you must disable interrupts/BH when
> + * producing.
> + */
>   static inline void *ptr_ring_consume(struct ptr_ring *r)
>   {
>   	void *ptr;
> @@ -357,7 +367,7 @@ static inline void **__ptr_ring_swap_queue(struct ptr_ring *r, void **queue,
>   	void **old;
>   	void *ptr;
>   
> -	while ((ptr = ptr_ring_consume(r)))
> +	while ((ptr = __ptr_ring_consume(r)))
>   		if (producer < size)
>   			queue[producer++] = ptr;
>   		else if (destroy)
> @@ -372,6 +382,12 @@ static inline void **__ptr_ring_swap_queue(struct ptr_ring *r, void **queue,
>   	return old;
>   }
>   
> +/*
> + * Note: producer lock is nested within consumer lock, so if you
> + * resize you must make sure all uses nest correctly.
> + * In particular if you consume ring in interrupt or BH context, you must
> + * disable interrupts/BH when doing so.
> + */
>   static inline int ptr_ring_resize(struct ptr_ring *r, int size, gfp_t gfp,
>   				  void (*destroy)(void *))
>   {
> @@ -382,17 +398,25 @@ static inline int ptr_ring_resize(struct ptr_ring *r, int size, gfp_t gfp,
>   	if (!queue)
>   		return -ENOMEM;
>   
> -	spin_lock_irqsave(&(r)->producer_lock, flags);
> +	spin_lock_irqsave(&(r)->consumer_lock, flags);
> +	spin_lock(&(r)->producer_lock);
>   
>   	old = __ptr_ring_swap_queue(r, queue, size, gfp, destroy);
>   
> -	spin_unlock_irqrestore(&(r)->producer_lock, flags);
> +	spin_unlock(&(r)->producer_lock);
> +	spin_unlock_irqrestore(&(r)->consumer_lock, flags);
>   
>   	kfree(old);
>   
>   	return 0;
>   }
>   
> +/*
> + * Note: producer lock is nested within consumer lock, so if you
> + * resize you must make sure all uses nest correctly.
> + * In particular if you consume ring in interrupt or BH context, you must
> + * disable interrupts/BH when doing so.
> + */
>   static inline int ptr_ring_resize_multiple(struct ptr_ring **rings, int nrings,
>   					   int size,
>   					   gfp_t gfp, void (*destroy)(void *))
> @@ -412,10 +436,12 @@ static inline int ptr_ring_resize_multiple(struct ptr_ring **rings, int nrings,
>   	}
>   
>   	for (i = 0; i < nrings; ++i) {
> -		spin_lock_irqsave(&(rings[i])->producer_lock, flags);
> +		spin_lock_irqsave(&(rings[i])->consumer_lock, flags);
> +		spin_lock(&(rings[i])->producer_lock);
>   		queues[i] = __ptr_ring_swap_queue(rings[i], queues[i],
>   						  size, gfp, destroy);
> -		spin_unlock_irqrestore(&(rings[i])->producer_lock, flags);
> +		spin_unlock(&(rings[i])->producer_lock);
> +		spin_unlock_irqrestore(&(rings[i])->consumer_lock, flags);
>   	}
>   
>   	for (i = 0; i < nrings; ++i)

      reply	other threads:[~2017-02-13  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 22:31 Michael S. Tsirkin
2017-02-13  5:04 ` Jason Wang [this message]

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=0aa7f7fc-3c10-2927-15d6-b061ea1add1f@redhat.com \
    --to=jasowang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=stable@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®