Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Hugo Mildenberger <Hugo.Mildenberger@t-online.de>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: ulogd2 patch
Date: Fri, 06 Jun 2008 01:29:34 +0200	[thread overview]
Message-ID: <484876DE.8070807@netfilter.org> (raw)
In-Reply-To: <200803221533.35790.Hugo.Mildenberger@t-online.de>

Hi Hugo,

Hugo Mildenberger wrote:
> Pablo,
> 
> is the ulogd2 project maintained anymore? Or is it a 
> dead project? I have a big patch ready.

It's alive, still under development. We plan to release a new beta soon.

> *fix a number heap corruption issues in ulogd2
> 
> *provide a module invariant checking function which 
> warns e.g. about issues like possible heap corruption 
> by suspect module implementations
> 
> *provide rewritten, state driven config file parser 
> based on flex capable of detecting wrongly spelled or 
> obsoleted parameters in config sections.
> 
> *provide named stacks as an optional feature (which may 
> be used as a stem for generating output filenames, 
> while it is already used for more clear error messages)
> 
> *add SIGUSR1 (reconfigure) support for all existing 
> modules
> 
> *corrected some SIGUSR1 logfile reopen issues
> 
> *introduce gcc printf-style argument checking on 
> ulogd_log function
> 
> *include lineno and filename information in ulogd 
> messages

Such a patchset would be great to have before releasing 2.0beta2 (we're
on the way to do it).

> I waited for the patches provided by eric Leblond in 
> netfilter-devel to be included in svn, but there are 
> none until today. So, what is the correct way to send a 
> patch upstream? 

Any plan to post it to the netfilter-devel ML?

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers


           reply	other threads:[~2008-06-05 23:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200803221533.35790.Hugo.Mildenberger@t-online.de>]

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=484876DE.8070807@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=Hugo.Mildenberger@t-online.de \
    --cc=netfilter-devel@vger.kernel.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