Re: Negating limit

[Sven Anders <anders@anduras.de>]

[-- Attachment #1: Type: text/plain, Size: 1780 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick wrote:

>> Here is a patch to allow a negated "limit", so we can match above and below the
>> limit.
>>
>> It adds a new "flags" variable after the burst. I'm not sure, if I can add it
>> after the "*master" variable, so I added it here.
>> Does this preserve compatibility, because anything after is only used by the kernel?
> 
> No, unfortunately there is no way to add a new variable to that struct
> without breaking compatibility. You could add a new revision, but I
> would like to think about Massimiliano Hofer's patch before that,
> if we do something like that we can get rid of the "master" pointer
> with the new revision.

What do you mean with "new revision"? A new match named "limit2"?

Which of Massimiliano's patches do you mean? The "support for entry data" patch?

To understand correctly:

 Is it not possible under any circumstances to add new variables to a match info
 struct or is the problem the "master" variable?

 If so what is the "master" variable for?

 As far as I understand the size of the "match info struct" passed from the
 userspace must exactly match the size of the kernels "match info struct".
 Right?

Regards
 Sven Anders

- --
 Sven Anders <anders@anduras.de>                 () Ascii Ribbon Campaign
                                                 /\ Support plain text e-mail
 ANDURAS service solutions AG
 Innstraße 71 - 94036 Passau - Germany
 Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEh+oQ5lKZ7Feg4EcRAvHeAJ9JD1tBGvLhZwETVaEpgj/KPZe3KACfcUhG
2/TN39WZ3JjJjwye4xW84i8=
=GIIo
-----END PGP SIGNATURE-----