netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [iptables PATCH 1/2] Revert "extensions: string: Clarify description of --to"
Date: Tue, 24 Oct 2023 13:43:56 +0200	[thread overview]
Message-ID: <20231024114357.23271-2-phil@nwl.cc> (raw)
In-Reply-To: <20231024114357.23271-1-phil@nwl.cc>

This reverts commit 920ece2b392fb83bd26416e0e6f8f6a847aacbaa.

Signed-off-by: Phil Sutter <phil@nwl.cc>
---
 extensions/libxt_string.man | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/extensions/libxt_string.man b/extensions/libxt_string.man
index efdda492ae78d..2a470ece19c9d 100644
--- a/extensions/libxt_string.man
+++ b/extensions/libxt_string.man
@@ -7,13 +7,9 @@ Select the pattern matching strategy. (bm = Boyer-Moore, kmp = Knuth-Pratt-Morri
 Set the offset from which it starts looking for any matching. If not passed, default is 0.
 .TP
 \fB\-\-to\fP \fIoffset\fP
-Set the offset up to which should be scanned. If the pattern does not start
-within this offset, it is not considered a match.
+Set the offset up to which should be scanned. That is, byte \fIoffset\fP-1
+(counting from 0) is the last one that is scanned.
 If not passed, default is the packet size.
-A second function of this parameter is instructing the kernel how much data
-from the packet should be provided. With non-linear skbuffs (e.g. due to
-fragmentation), a pattern extending past this offset may not be found. Also see
-the related note below about Boyer-Moore algorithm in these cases.
 .TP
 [\fB!\fP] \fB\-\-string\fP \fIpattern\fP
 Matches the given pattern.
-- 
2.41.0


  reply	other threads:[~2023-10-24 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 11:43 [iptables PATCH 0/2] Fix up string match man page Phil Sutter
2023-10-24 11:43 ` Phil Sutter [this message]
2023-10-24 11:43 ` [iptables PATCH 2/2] extensions: string: Clarify description of --to Phil Sutter
2023-10-25 15:27 ` [iptables PATCH 0/2] Fix up string match man page Phil Sutter

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=20231024114357.23271-2-phil@nwl.cc \
    --to=phil@nwl.cc \
    --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).