linux-kernel - [PATCH 0/2] key payload access with just rcu_read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 22 Feb 2017 23:54:25 +0100
From:   Jan Stancek <jstancek@...hat.com>
To:     dhowells@...hat.com
Cc:     linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
        jstancek@...hat.com, bcodding@...hat.com, asavkov@...hat.com
Subject: [PATCH 0/2] key payload access with just rcu_read_lock()

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