linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Vasily Averin <vvs@virtuozzo.com>
Cc: Jan Kara <jack@suse.cz>,
	linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	Jan Kara <jack@suse.com>
Subject: Re: [PATCH 1/1] jbd2_seq_info_next should increase position index
Date: Thu, 23 Jan 2020 15:02:43 +0100	[thread overview]
Message-ID: <20200123140243.GA7914@quack2.suse.cz> (raw)
In-Reply-To: <43e6a168-63b6-4a82-7b3d-5dd676b9f9bb@virtuozzo.com>

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!

								Honza

> 
> I've reproduced it on last ubuntu kernel
> 
> $ uname -a
> Linux vvs-ws 5.3.0-24-generic #26~18.04.2-Ubuntu SMP Tue Nov 26 12:34:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> 
> $ q=;while read -r r;do echo "$((++q)) $r";done </proc/fs/jbd2/sda4-8/info  | head -20
> 1 151327 transactions (132200 requested), each up to 65536 blocks
> 2 average:
> 3 0ms waiting for transaction
> 4 0ms request delay
> 5 3816ms running transaction
> 6 0ms transaction was being locked
> 7 0ms flushing data (in ordered mode)
> 8 36ms logging transaction
> 9 29753us average transaction commit time
> 10 1587 handles per transaction
> 11 32 blocks per transaction
> 12 33 logged blocks per transaction
> 13 151327 transactions (132200 requested), each up to 65536 blocks
> 14 151327 transactions (132200 requested), each up to 65536 blocks
> 15 151327 transactions (132200 requested), each up to 65536 blocks
> 16 151327 transactions (132200 requested), each up to 65536 blocks
> 17 151327 transactions (132200 requested), each up to 65536 blocks
> 18 151327 transactions (132200 requested), each up to 65536 blocks
> 19 151327 transactions (132200 requested), each up to 65536 blocks
> 20 151327 transactions (132200 requested), each up to 65536 blocks
> 
> >> https://bugzilla.kernel.org/show_bug.cgi?id=206283
> >> Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
> >> ---
> >>  fs/jbd2/journal.c | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> >> index 5e408ee..b3e2433 100644
> >> --- a/fs/jbd2/journal.c
> >> +++ b/fs/jbd2/journal.c
> >> @@ -982,6 +982,7 @@ static void *jbd2_seq_info_start(struct seq_file *seq, loff_t *pos)
> >>  
> >>  static void *jbd2_seq_info_next(struct seq_file *seq, void *v, loff_t *pos)
> >>  {
> >> +	(*pos)++;
> >>  	return NULL;
> >>  }
> >>  
> >> -- 
> >> 1.8.3.1
> >>
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  reply	other threads:[~2020-01-23 14:12 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 [this message]
2020-01-25  7:31       ` Theodore Y. Ts'o

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=20200123140243.GA7914@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --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).