linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	bcodding@redhat.com, asavkov@redhat.com
Subject: Re: [PATCH 0/2] key payload access with just rcu_read_lock()
Date: Tue, 28 Feb 2017 04:12:48 -0500 (EST)	[thread overview]
Message-ID: <275589099.574523.1488273168507.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <25524.1488241404@warthog.procyon.org.uk>



----- Original Message -----
> Jan Stancek <jstancek@redhat.com> wrote:
> 
> > Looks like there are still couple users that need updating,
> > I'm hitting following compilation error:
> 
> Aargh - I remembered to grep for rcu_dereference_key() but not
> user_key_payload().
> 
> How about the attached?

v2 builds OK (on top of 4.10), "suspicious RCU usage"
warning is gone and NFS connectathon is PASS-ing cleanly.

Regards,
Jan

  reply	other threads:[~2017-02-28  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 22:54 [PATCH 0/2] key payload access with just rcu_read_lock() Jan Stancek
2017-02-22 22:54 ` [PATCH 1/2] KEYS: add user_key_payload_rcu() Jan Stancek
2017-02-22 22:54 ` [PATCH 2/2] NFS: use user_key_payload_rcu() in RCU read-side section Jan Stancek
2017-02-27 22:04 ` [PATCH 0/2] key payload access with just rcu_read_lock() David Howells
2017-02-27 22:47   ` Jan Stancek
2017-02-28  0:23   ` David Howells
2017-02-28  9:12     ` Jan Stancek [this message]
2017-02-28 10:28   ` David Howells
2017-02-28 14:20     ` Jan Stancek
2017-03-01  9:40     ` David Howells
2017-03-01  9:45       ` Jan Stancek

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=275589099.574523.1488273168507.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=asavkov@redhat.com \
    --cc=bcodding@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).