linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Vasily Averin <vvs@virtuozzo.com>,
	linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>
Subject: Re: [PATCH 1/1] jbd2_seq_info_next should increase position index
Date: Sat, 25 Jan 2020 02:31:09 -0500	[thread overview]
Message-ID: <20200125073109.GH1108497@mit.edu> (raw)
In-Reply-To: <20200123140243.GA7914@quack2.suse.cz>

On Thu, Jan 23, 2020 at 03:02:43PM +0100, Jan Kara wrote:
> On Thu 23-01-20 14:30:14, Vasily Averin wrote:
> > 
> > 
> > On 1/23/20 2:15 PM, Jan Kara wrote:
> > > On Thu 23-01-20 12:05:10, Vasily Averin wrote:
> > >> if seq_file .next fuction does not change position index,
> > >> read after some lseek can generate unexpected output.
> > >>
> > >> Script below generates endless output
> > >>  $ q=;while read -r r;do echo "$((++q)) $r";done </proc/fs/jbd2/DEV/info
> > > 
> > > I've just tried and this works for me just fine with openSUSE 15.1
> > > (4.12.14-based) kernel. Is it some recent regression?
> > 
> > I think it depends on 
> > commit 1f4aace60b0e ("fs/seq_file.c: simplify seq_file iteration code and interface")
> > In OpenVz7 we got complain after backport of this patch.
> 
> I see. OK. So please add tag:
> 
> Fixes: 1f4aace60b0e ("fs/seq_file.c: simplify seq_file iteration code and interface")
> 
> likely also:
> 
> CC: stable@vger.kernel.org
> 
> and you can also add:
> 
> Reviewed-by: Jan Kara <jack@suse.cz>

Thanks, applied with the suggested tags.

						- Ted

      reply	other threads:[~2020-01-25  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  9:05 [PATCH 1/1] jbd2_seq_info_next should increase position index Vasily Averin
2020-01-23 11:15 ` Jan Kara
2020-01-23 11:30   ` Vasily Averin
2020-01-23 14:02     ` Jan Kara
2020-01-25  7:31       ` Theodore Y. Ts'o [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=20200125073109.GH1108497@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --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).