From: Vasily Averin <vvs@virtuozzo.com>
To: David Howells <dhowells@redhat.com>
Cc: 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 v2] keys: proc_keys_next should increase position index
Date: Sat, 1 Feb 2020 10:54:06 +0300 [thread overview]
Message-ID: <bb473a18-3241-9377-3bee-33d4e9381f3d@virtuozzo.com> (raw)
In-Reply-To: <265151.1580491178@warthog.procyon.org.uk>
On 1/31/20 8:19 PM, David Howells wrote:
> Vasily Averin <vvs@virtuozzo.com> wrote:
>> If seq_file .next fuction does not change position index,
> "function"
>> <<<< and whole last lien again
> "line"
>
> I can fix these up for you.
thank you!
>> https://bugzilla.kernel.org/show_bug.cgi?id=206283
>
> I wonder if this should have a tag - it looks kind of out of place without
> one, but I can't find one suggested.
Some maintainers of another subsystems asked me to add
Cc: stable@vger.kernel.org
Fixes: 1f4aace60b0e ("fs/seq_file.c: simplify seq_file iteration code ...")
however frankly speaking I do not think it is required in this case.
Thank you,
Vasily Averin
next prev parent reply other threads:[~2020-02-01 7:54 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
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 [this message]
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=bb473a18-3241-9377-3bee-33d4e9381f3d@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=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 \
/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).