From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Peter Volkov <pva@gentoo.org>
Cc: netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: ipset-6.9.1: 3.0.4 kernel tests failure
Date: Mon, 19 Sep 2011 14:41:14 +0100 [thread overview]
Message-ID: <4E77467A.6070500@googlemail.com> (raw)
In-Reply-To: <1316438977.7764.6.camel@tablet>
> BTW, in general is it better to use in-kernel modules or kernel modules
> bundled with ipset? Personally I'd better pushed required patches into
> our kernels and suggested users to use them, but where it's better to
> pull such patches from?
>
My own personal preference since last year has been to integrate the
kernel modules as part of the kernel built and then use modified .spec
file to build ipset (the userspace executable).
There are a couple of reasons for this, not least because every time I
need to build/change the kernel (and that happens more often than
building ipset - at least in my case, as I am testing different things
in the kernel for different machines at one time) I have to reinstall
the buildsys packages (I use Fedora) and tailor them for the new kernel
in order to allow ipset kernel modules to be built, then rebuild ipset
(userspace) as well - too much hassle.
What I do to avoid all that is create a patch based on the ipset kernel
module sources as well as the ipset Kconfig/Kbuild menu options and then
integrate that patch as part of the kernel built. That has never failed
except the last time with the above version of ipset, but Jozsef
provided a quick work-around and I am happy with it - it works!
next prev parent reply other threads:[~2011-09-19 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 13:29 ipset-6.9.1: 3.0.4 kernel tests failure Peter Volkov
2011-09-19 13:41 ` Mr Dash Four [this message]
2011-09-19 15:08 ` Jozsef Kadlecsik
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=4E77467A.6070500@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pva@gentoo.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 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.