All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira <pablo@eurodev.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 1/2] string match for iptables
Date: Sat, 20 Aug 2005 18:35:54 +0200	[thread overview]
Message-ID: <43075BEA.1030701@trash.net> (raw)
In-Reply-To: <43075517.3070405@eurodev.net>

Pablo Neira wrote:
> Here comes the iptables string match since the textsearch infrastructure
> went into 2.6.13. This adds to iptables the ability of looking for given
> patterns in packets. I'll be happy to see this stuff in Davem's 2.6.14
> tree ;)

> +struct ipt_string_info
> +{
> +	u_int16_t		from_offset;
> +	u_int16_t		to_offset;
> +	char			algo[IPT_STRING_MAX_ALGO_NAME_SIZE];
> +	char			pattern[IPT_STRING_MAX_PATTERN_SIZE];
> +	u_int8_t		patlen;
> +	u_int8_t		invert;
> +	struct ts_config	*config;
> +};

Embedding a pointer in the struct causes different alignment depending
on the wordsize and doesn't work in mixed 64/32 bit environments.
Please use __attribute__((aligned(8))) to prevent this.

Otherwise, it looks good.

  reply	other threads:[~2005-08-20 16:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20 16:06 [PATCH 1/2] string match for iptables Pablo Neira
2005-08-20 16:35 ` Patrick McHardy [this message]
2005-08-20 20:14   ` David S. Miller
2005-08-21 13:55     ` Patrick McHardy
2005-08-21 22:34       ` David S. Miller
2005-08-22  0:13         ` Patrick McHardy
2005-08-22  2:14           ` David S. Miller
2005-08-25 10:42     ` Harald Welte
2005-08-25 16:54       ` Martin Josefsson
2005-08-25 17:19         ` Martin Josefsson
2005-08-26 12:00           ` Patrick McHardy
2005-08-26 13:27             ` DaveM get's removed from Cc (was Re: [PATCH 1/2] string match for iptables) Harald Welte
2005-08-26 15:21               ` Phil Oester
2005-08-26 18:33                 ` Harald Welte

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=43075BEA.1030701@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.