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: Wed, 1 Mar 2017 04:45:23 -0500 (EST) [thread overview]
Message-ID: <502629911.1125748.1488361523729.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <11141.1488361213@warthog.procyon.org.uk>
----- Original Message -----
> From: "David Howells" <dhowells@redhat.com>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, bcodding@redhat.com,
> asavkov@redhat.com
> Sent: Wednesday, 1 March, 2017 10:40:13 AM
> Subject: Re: [PATCH 0/2] key payload access with just rcu_read_lock()
>
> Jan Stancek <jstancek@redhat.com> wrote:
>
> > That problem didn't show up with my NFS based reproducer.
> > I re-run it again with latest version of your patch, plus also
> > keyutils testsuite. Both completed OK for me, dmesg looks clean.
>
> Can I put you down as a Tested-by?
Yes. Thanks for having a look at this.
Regards,
Jan
prev parent reply other threads:[~2017-03-01 13:39 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
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 [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=502629911.1125748.1488361523729.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 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.