From: Pablo Neira Ayuso <pablo@gnumonks.org>
To: Fiedler Roman <Roman.Fiedler@ait.ac.at>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: ulogd syslogemu output garbage after kernel update (32 to 64bit)
Date: Thu, 13 Sep 2012 13:09:55 +0200 [thread overview]
Message-ID: <20120913110955.GA3914@1984> (raw)
In-Reply-To: <9F69795E29C890408AC2DAF646C89BB379DA5476A8@MAILBOX.arc.local>
On Thu, Sep 13, 2012 at 09:42:24AM +0200, Fiedler Roman wrote:
> > -----Ursprüngliche Nachricht-----
> > Von: Fiedler Roman
> > Gesendet: Montag, 10. September 2012 08:37
> > An: netfilter-devel@vger.kernel.org
> > Betreff: ulogd syslogemu output garbage after kernel update (32 to 64bit)
> >
> > Hello list,
> >
> > In short: Could 32-bit ulogd run on 64-bit kernel without failing?
>
> Has any one an educated guess, if that could work? Are netlink data-structures machine-arch dependent and hence a 32-bit ulogd cannot process a 64-bit netlink message?
Netlink is aligned to 32-bits, no matter if arch is 32-bits/64-bits.
So the short answer is yes, it should work.
You'll have to debug this issue further if you want us to help.
Moreover, as Jozsef mentioned, we're targeting to ulogd2. Consider
that ulogd has entered EOL.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-13 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 7:42 AW: ulogd syslogemu output garbage after kernel update (32 to 64bit) Fiedler Roman
2012-09-13 8:32 ` Jozsef Kadlecsik
2012-09-13 11:09 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-10 6:36 Fiedler Roman
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=20120913110955.GA3914@1984 \
--to=pablo@gnumonks.org \
--cc=Roman.Fiedler@ait.ac.at \
--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;
as well as URLs for NNTP newsgroup(s).