From: Florian Westphal <fw@strlen.de>
To: Oleg <lego12239@yandex.ru>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: libnetfilter_queue & multithreading
Date: Mon, 24 Jul 2017 11:44:51 +0200 [thread overview]
Message-ID: <20170724094451.GC26175@breakpoint.cc> (raw)
In-Reply-To: <20170724094009.GB19358@legohost>
Oleg <lego12239@yandex.ru> wrote:
> On Sat, Jul 22, 2017 at 06:38:55PM +0200, Florian Westphal wrote:
> > Oleg <lego12239@yandex.ru> wrote:
> > > static void*
> > > thread_start(void *data)
> > > {
> > > struct nfq_handle *h;
> > > int fd, n;
> > > static char *pkt_buf;
> >
> > static? Looks buggy...
>
> Hm, why :-)? This function must be local and shouldn't be seen in other
> source files.
I was talking about pkt_buf.
next prev parent reply other threads:[~2017-07-24 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 13:08 libnetfilter_queue & multithreading Oleg
2017-07-22 16:38 ` Florian Westphal
2017-07-24 9:40 ` Oleg
2017-07-24 9:44 ` Florian Westphal [this message]
2017-07-24 10:11 ` Oleg
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=20170724094451.GC26175@breakpoint.cc \
--to=fw@strlen.de \
--cc=lego12239@yandex.ru \
--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).