public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Averin <vvs@virtuozzo.com>
To: Andrew Morton <akpm@linux-foundation.org>, Qian Cai <cai@lca.pw>
Cc: linux-kernel@vger.kernel.org, dave@stgolabs.net,
	longman@redhat.com, manfred@colorfullife.com, mingo@redhat.com,
	mm-commits@vger.kernel.org, neilb@suse.com,
	oberpar@linux.ibm.com, rostedt@goodmis.org,
	viro@zeniv.linux.org.uk, netfilter-devel@vger.kernel.org,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: + seq_read-info-message-about-buggy-next-functions.patch added to -mm tree
Date: Tue, 3 Mar 2020 08:36:57 +0300	[thread overview]
Message-ID: <90db01f0-e8b4-0acb-cd09-d79825f2c03d@virtuozzo.com> (raw)
In-Reply-To: <20200302124219.eaf3d18422b76ff2196d9ce8@linux-foundation.org>



On 3/2/20 11:42 PM, Andrew Morton wrote:
> On Mon, 02 Mar 2020 14:31:48 -0500 Qian Cai <cai@lca.pw> wrote:
> 
>> On Mon, 2020-03-02 at 13:20 -0500, Qian Cai wrote:
>>> This patch spams the console like crazy while reading sysfs,
>>>
>>> # dmesg | grep 'buggy seq_file' | wc -l
>>> 4204
>>>
>>> [ 9505.321981] LTP: starting read_all_proc (read_all -d /proc -q -r 10)
>>> [ 9508.222934] buggy seq_file .next function xt_match_seq_next [x_tables] did
>>> not updated position index
>>> [ 9508.223319] buggy seq_file .next function xt_match_seq_next [x_tables] did
>>> not updated position index
>>> [ 9508.223654] buggy seq_file .next function xt_match_seq_next [x_tables] did
>>> not updated position index
>>> [ 9508.223994] buggy seq_file .next function xt_match_seq_next [x_tables] did
>>> not updated position index
>>> [ 9508.224337] buggy seq_file .next function xt_match_seq_next [x_tables] did
>>> not updated position index

It should be fixed by following patch-set submitted to Netfilter-Devel mailing list
[PATCH v2 0/4] netfilter: seq_file .next functions should increase position index
https://lore.kernel.org/netfilter-devel/497a82c1-7b6a-adf4-a4ce-df46fe436aae@virtuozzo.com/T/

>>>> --- a/fs/seq_file.c~seq_read-info-message-about-buggy-next-functions
>>>> +++ a/fs/seq_file.c
>>>> @@ -256,9 +256,12 @@ Fill:
>>>>  		loff_t pos = m->index;
>>>>  
>>>>  		p = m->op->next(m, p, &m->index);
>>>> -		if (pos == m->index)
>>>> -			/* Buggy ->next function */
>>>> +		if (pos == m->index) {
>>>> +			pr_info("buggy seq_file .next function %ps "
>>>> +				"did not updated position index\n",
>>>> +				m->op->next);
>>
>> This?
>>
>> s/pr_info/pr_info_ratelimited/
>>
> 
> Fair enough - I made that change.
> 

      reply	other threads:[~2020-03-03  5:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200226035621.4NlNn738T%akpm@linux-foundation.org>
2020-03-02 18:20 ` + seq_read-info-message-about-buggy-next-functions.patch added to -mm tree Qian Cai
2020-03-02 19:31   ` Qian Cai
2020-03-02 20:42     ` Andrew Morton
2020-03-03  5:36       ` Vasily Averin [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=90db01f0-e8b4-0acb-cd09-d79825f2c03d@virtuozzo.com \
    --to=vvs@virtuozzo.com \
    --cc=akpm@linux-foundation.org \
    --cc=cai@lca.pw \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=manfred@colorfullife.com \
    --cc=mingo@redhat.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=oberpar@linux.ibm.com \
    --cc=pablo@netfilter.org \
    --cc=rostedt@goodmis.org \
    --cc=viro@zeniv.linux.org.uk \
    /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