From: Pablo Neira Ayuso <pablo@netfilter.org>
To: frank <frank@undermydesk.org>
Cc: netfilter@vger.kernel.org
Subject: Re: ulogd2 / segfault in ulogd_raw2packet_BASE.c with kernel 4.8.1
Date: Mon, 17 Oct 2016 21:34:06 +0200 [thread overview]
Message-ID: <20161017193406.GB24375@salvia> (raw)
In-Reply-To: <a3d68560-143a-7907-0440-6d6ce9698bdb@undermydesk.org>
On Tue, Oct 11, 2016 at 09:16:22AM +0200, frank wrote:
> Hi Eric,
> dear list,
>
> just a short update on this issue...
>
> There's someone over at LKML with the same issue and there
> seems to be fix for this on the way.
> Your earlier assumption about the kernel changes were true:
>
> http://www.gossamer-threads.com/lists/linux/kernel/2538445?do=post_view_threaded
I have just applied the fix for 4.8, will take a little while to
propagate this to -stable.
Meanwhile, oneliner patch to fix it is here:
http://patchwork.ozlabs.org/patch/680773/
prev parent reply other threads:[~2016-10-17 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 21:31 ulogd2 / segfault in ulogd_raw2packet_BASE.c with kernel 4.8.1 Frank Reppin
2016-10-09 23:26 ` Eric Leblond
2016-10-10 21:34 ` Frank Reppin
2016-10-11 7:16 ` frank
2016-10-16 20:11 ` Frank Reppin
2016-10-17 19:34 ` Pablo Neira Ayuso [this message]
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=20161017193406.GB24375@salvia \
--to=pablo@netfilter.org \
--cc=frank@undermydesk.org \
--cc=netfilter@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