From: Vasily Averin <vvs@virtuozzo.com>
To: coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>
Subject: [PATCH 0/4] netfilter: seq_file .next functions should increase position index
Date: Thu, 23 Jan 2020 10:25:24 +0300 [thread overview]
Message-ID: <497a82c1-7b6a-adf4-a4ce-df46fe436aae@virtuozzo.com> (raw)
In Aug 2018 NeilBrown noticed
commit 1f4aace60b0e ("fs/seq_file.c: simplify seq_file iteration code and interface")
"Some ->next functions do not increment *pos when they return NULL...
Note that such ->next functions are buggy and should be fixed.
A simple demonstration is
dd if=/proc/swaps bs=1000 skip=1
Choose any block size larger than the size of /proc/swaps. This will
always show the whole last line of /proc/swaps"
Described problem is still actual. If you make lseek into middle of last output line
following read will output end of last line and whole last line once again.
$ dd if=/proc/swaps bs=1 # usual output
Filename Type Size Used Priority
/dev/dm-0 partition 4194812 97536 -2
104+0 records in
104+0 records out
104 bytes copied
$ dd if=/proc/swaps bs=40 skip=1 # last line was generated twice
dd: /proc/swaps: cannot skip to specified offset
v/dm-0 partition 4194812 97536 -2
/dev/dm-0 partition 4194812 97536 -2
3+1 records in
3+1 records out
131 bytes copied
There are lot of other affected files, I've found 30+ including
/proc/net/ip_tables_matches and /proc/sysvipc/*
This patch-set fixes files related to netfilter@
https://bugzilla.kernel.org/show_bug.cgi?id=206283
Vasily Averin (4):
ct_cpu_seq_next should increase position index
synproxy_cpu_seq_next should increase position index
recent_seq_next should increase position index
xt_mttg_seq_next should increase position index
net/netfilter/nf_conntrack_standalone.c | 2 +-
net/netfilter/nf_synproxy_core.c | 2 +-
net/netfilter/x_tables.c | 6 +++---
net/netfilter/xt_recent.c | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-01-23 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 7:25 Vasily Averin [this message]
2020-02-25 7:05 ` [PATCH v2 0/4] netfilter: seq_file .next functions should increase position index Vasily Averin
2020-03-04 1:26 ` Pablo Neira Ayuso
2020-02-25 7:05 ` [PATCH v2 1/4] ct_cpu_seq_next " Vasily Averin
2020-02-25 7:05 ` [PATCH v2 2/4] synproxy_cpu_seq_next " Vasily Averin
2020-02-25 7:06 ` [PATCH v2 3/4] recent_seq_next " Vasily Averin
2020-02-25 7:07 ` [PATCH v2 4/4] xt_mttg_seq_next " Vasily Averin
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=497a82c1-7b6a-adf4-a4ce-df46fe436aae@virtuozzo.com \
--to=vvs@virtuozzo.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).