All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: dhowells@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	jstancek@redhat.com, bcodding@redhat.com, asavkov@redhat.com
Subject: [PATCH 0/2] key payload access with just rcu_read_lock()
Date: Wed, 22 Feb 2017 23:54:25 +0100	[thread overview]
Message-ID: <cover.1487802542.git.jstancek@redhat.com> (raw)

Hi David,

this is a follow-up for "suspicious RCU usage" warning described
in these 2 linux-nfs threads:
  http://marc.info/?t=147558830300003&r=1&w=2
  http://marc.info/?t=148776770500001&r=1&w=2

Did you have something like in mind?

Thanks,
Jan

Jan Stancek (2):
  KEYS: add user_key_payload_rcu()
  NFS: use user_key_payload_rcu() in RCU read-side section

 Documentation/security/keys.txt | 5 +++++
 fs/nfs/nfs4idmap.c              | 2 +-
 include/keys/user-type.h        | 5 +++++
 include/linux/key.h             | 3 +++
 4 files changed, 14 insertions(+), 1 deletion(-)

-- 
1.8.3.1


             reply	other threads:[~2017-02-22 22:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 22:54 Jan Stancek [this message]
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
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=cover.1487802542.git.jstancek@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 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.