From: David Howells <dhowells@redhat.com>
To: Vasily Averin <vvs@virtuozzo.com>
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH 1/1] proc_keys_next should increase position index
Date: Mon, 27 Jan 2020 11:39:34 +0000 [thread overview]
Message-ID: <1451508.1580125174@warthog.procyon.org.uk> (raw)
In-Reply-To: <af9dcaa7-6e4f-281a-2bae-fb605cc55d2d@virtuozzo.com>
I don't see the effect you're talking about with /proc/keys. I see the
following:
[root@andromeda ~]# dd if=/proc/keys bs=40 skip=1
dd: /proc/keys: cannot skip to specified offset
and then it follows up with the normal content with no obvious duplicates (the
lines are numbered ascendingly in the first column).
I think I may be being confused by what you mean by "the last line".
David
next prev parent reply other threads:[~2020-01-27 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 6:25 [PATCH 1/1] proc_keys_next should increase position index Vasily Averin
2020-01-27 11:39 ` David Howells [this message]
2020-01-27 19:27 ` Vasily Averin
2020-01-30 10:16 ` [PATCH v2] keys: " Vasily Averin
2020-01-31 17:19 ` David Howells
2020-02-01 7:54 ` Vasily Averin
2020-01-30 8:42 ` [PATCH 1/1] " Jarkko Sakkinen
2020-01-30 8:38 ` Jarkko Sakkinen
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=1451508.1580125174@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=vvs@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).