From: Patrick McHardy <kaber@trash.net>
To: Linmujia <linmujia@huawei.com>
Cc: "pablo@netfilter.org" <pablo@netfilter.org>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft] null pointer exception
Date: Sat, 28 Nov 2015 12:20:05 +0000 [thread overview]
Message-ID: <20151128122004.GA17106@macbook.localdomain> (raw)
In-Reply-To: <0A900C78B9F2324AB7F4F7A51D1A2F857797855C@szxema505-mbs.china.huawei.com>
On 28.11, Linmujia wrote:
> Hi,I think I find out why my last patch stoped the execution of the tool,
> If "stmt_reject_gen_dependency" do not get any payload (payload=null) , it can not call "payload_gen_dependency ",it will cause null pointer exception.
>
It is really unclear what you're trying to do. You've sent multiple patches
of which every single one was competely wrong and randomly changing return
values.
How about you start by explaining what you're trying to do?
prev parent reply other threads:[~2015-11-28 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 1:55 [PATCH nft] null pointer exception Linmujia
2015-11-28 12:20 ` Patrick McHardy [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=20151128122004.GA17106@macbook.localdomain \
--to=kaber@trash.net \
--cc=linmujia@huawei.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).