From: Patrick McHardy <kaber@trash.net>
To: Joonwoo Park <joonwpark81@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>,
Thomas Graf <tgraf@suug.ch>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH 6/8] netfilter: fix string extension for case insensitive pattern matching
Date: Sat, 21 Jun 2008 10:16:08 +0200 [thread overview]
Message-ID: <485CB8C8.90106@trash.net> (raw)
In-Reply-To: <1214034858-1378-1-git-send-email-joonwpark81@gmail.com>
Joonwoo Park wrote:
> icase of xt_string_info indicates case [in]sensitive matching.
> netfilter can find cmd.exe, Cmd.exe, cMd.exe and etc easily.
>
> Signed-off-by: Joonwoo Park <joonwpark81@gmail.com>
> ---
> include/linux/netfilter/xt_string.h | 1 +
> net/netfilter/xt_string.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/netfilter/xt_string.h b/include/linux/netfilter/xt_string.h
> index bb21dd1..dfd347f 100644
> --- a/include/linux/netfilter/xt_string.h
> +++ b/include/linux/netfilter/xt_string.h
> @@ -12,6 +12,7 @@ struct xt_string_info
> char pattern[XT_STRING_MAX_PATTERN_SIZE];
> u_int8_t patlen;
> u_int8_t invert;
> + u_int8_t icase;
>
> /* Used internally by the kernel */
> struct ts_config __attribute__((aligned(8))) *config;
A few words for the changelog why this won't break compatibility
by changing the data structure would be nice, especially
considering CRIS that doesn't perform any padding itself (you
might be lucky though because of aligned attribute, but please
verify that yourself).
next prev parent reply other threads:[~2008-06-21 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 7:54 [PATCH 6/8] netfilter: fix string extension for case insensitive pattern matching Joonwoo Park
2008-06-21 8:16 ` Patrick McHardy [this message]
2008-06-29 14:29 ` Jan Engelhardt
2008-06-30 18:44 ` Joonwoo Park
2008-06-30 19:09 ` Jan Engelhardt
2008-06-30 19:32 ` Joonwoo Park
2008-06-30 20:04 ` Patrick McHardy
2008-07-01 7:10 ` Joonwoo Park
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=485CB8C8.90106@trash.net \
--to=kaber@trash.net \
--cc=joonwpark81@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tgraf@suug.ch \
/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).