mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>,
	Kees Cook <keescook@chromium.org>,
	Tony Luck <tony.luck@intel.com>
Subject: Re: pstore/core: drop cmpxchg based updates
Date: Thu, 8 Sep 2016 14:32:05 -0700	[thread overview]
Message-ID: <20160908213205.GA4276@roeck-us.net> (raw)
In-Reply-To: <20160824130935.23110-1-bigeasy@linutronix.de>

On Wed, Aug 24, 2016 at 03:09:35PM +0200, Sebastian Andrzej Siewior wrote:
> I have here a FPGA behind PCIe which exports SRAM which I use for
> pstore. Now it seems that the FPGA no longer supports cmpxchg based
> updates and writes back 0xff…ff and returns the same.  This leads to
> crash during crash rendering pstore useless.
> Since I doubt that there is much benefit from using cmpxchg() here, I am
> dropping this atomic access and use the spinlock based version.
> 
> Cc: Anton Vorontsov <anton@enomsg.org>
> Cc: Colin Cross <ccross@android.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Tony Luck <tony.luck@intel.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Tested-by: Rabin Vincent <rabinv@axis.com>

Great, one item taken off my task list.

As Rabin suggested, this patch is needed for at least some ARM chips,
and should be applied to stable releases.

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
>  fs/pstore/ram_core.c | 43 ++-----------------------------------------
>  1 file changed, 2 insertions(+), 41 deletions(-)
> 
> diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c
> index 76c3f80efdfa..4bae54bb61cd 100644
> --- a/fs/pstore/ram_core.c
> +++ b/fs/pstore/ram_core.c
> @@ -47,39 +47,6 @@ static inline size_t buffer_start(struct persistent_ram_zone *prz)
>  	return atomic_read(&prz->buffer->start);
>  }
>  
> -/* increase and wrap the start pointer, returning the old value */
> -static size_t buffer_start_add_atomic(struct persistent_ram_zone *prz, size_t a)
> -{
> -	int old;
> -	int new;
> -
> -	do {
> -		old = atomic_read(&prz->buffer->start);
> -		new = old + a;
> -		while (unlikely(new >= prz->buffer_size))
> -			new -= prz->buffer_size;
> -	} while (atomic_cmpxchg(&prz->buffer->start, old, new) != old);
> -
> -	return old;
> -}
> -
> -/* increase the size counter until it hits the max size */
> -static void buffer_size_add_atomic(struct persistent_ram_zone *prz, size_t a)
> -{
> -	size_t old;
> -	size_t new;
> -
> -	if (atomic_read(&prz->buffer->size) == prz->buffer_size)
> -		return;
> -
> -	do {
> -		old = atomic_read(&prz->buffer->size);
> -		new = old + a;
> -		if (new > prz->buffer_size)
> -			new = prz->buffer_size;
> -	} while (atomic_cmpxchg(&prz->buffer->size, old, new) != old);
> -}
> -
>  static DEFINE_RAW_SPINLOCK(buffer_lock);
>  
>  /* increase and wrap the start pointer, returning the old value */
> @@ -124,9 +91,6 @@ static void buffer_size_add_locked(struct persistent_ram_zone *prz, size_t a)
>  	raw_spin_unlock_irqrestore(&buffer_lock, flags);
>  }
>  
> -static size_t (*buffer_start_add)(struct persistent_ram_zone *, size_t) = buffer_start_add_atomic;
> -static void (*buffer_size_add)(struct persistent_ram_zone *, size_t) = buffer_size_add_atomic;
> -
>  static void notrace persistent_ram_encode_rs8(struct persistent_ram_zone *prz,
>  	uint8_t *data, size_t len, uint8_t *ecc)
>  {
> @@ -338,9 +302,9 @@ int notrace persistent_ram_write(struct persistent_ram_zone *prz,
>  		c = prz->buffer_size;
>  	}
>  
> -	buffer_size_add(prz, c);
> +	buffer_size_add_locked(prz, c);
>  
> -	start = buffer_start_add(prz, c);
> +	start = buffer_start_add_locked(prz, c);
>  
>  	rem = prz->buffer_size - start;
>  	if (unlikely(rem < c)) {
> @@ -426,9 +390,6 @@ static void *persistent_ram_iomap(phys_addr_t start, size_t size,
>  		return NULL;
>  	}
>  
> -	buffer_start_add = buffer_start_add_locked;
> -	buffer_size_add = buffer_size_add_locked;
> -
>  	if (memtype)
>  		va = ioremap(start, size);
>  	else

  parent reply	other threads:[~2016-09-08 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 13:09 [PATCH] " Sebastian Andrzej Siewior
2016-09-08 10:23 ` Rabin Vincent
2016-09-08 21:32 ` Guenter Roeck [this message]
2016-09-08 22:01   ` Kees Cook

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=20160908213205.GA4276@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=anton@enomsg.org \
    --cc=bigeasy@linutronix.de \
    --cc=ccross@android.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.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

Powered by JetHome