netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>
Subject: Re: [Patch net 2/3] net_sched: fix a memory leak in cls_tcindex
Date: Sun, 10 Feb 2019 23:19:46 -0800	[thread overview]
Message-ID: <CAM_iQpV=M18jeWfpFij=TT5YUnwzhyh8POkDx-diRB8BzefyuA@mail.gmail.com> (raw)
In-Reply-To: <201902111051.xRYMeLJl%fengguang.wu@intel.com>

On Sun, Feb 10, 2019 at 6:15 PM kbuild test robot <lkp@intel.com> wrote:
>
> Hi Cong,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on net/master]
>
> url:    https://github.com/0day-ci/linux/commits/Cong-Wang/net_sched-some-fixes-for-cls_tcindex/20190211-095057
> config: i386-randconfig-x002-201906 (attached as .config)
> compiler: gcc-8 (Debian 8.2.0-14) 8.2.0
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
>    net/sched/cls_tcindex.c: In function 'tcindex_alloc_perfect_hash':
> >> net/sched/cls_tcindex.c:301:22: error: 'struct tcf_exts' has no member named 'net'
>       cp->perfect[i].exts.net = net;

Yeah, looks like I missed the CONFIG_CLS_ACT=n case.

Let me think about how to fix it properly.

Thanks!

  parent reply	other threads:[~2019-02-11  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  1:47 [Patch net 0/3] net_sched: some fixes for cls_tcindex Cong Wang
2019-02-11  1:47 ` [Patch net 1/3] net_sched: fix a race condition in tcindex_destroy() Cong Wang
2019-02-11  1:47 ` [Patch net 2/3] net_sched: fix a memory leak in cls_tcindex Cong Wang
     [not found]   ` <201902111051.xRYMeLJl%fengguang.wu@intel.com>
2019-02-11  7:19     ` Cong Wang [this message]
2019-02-11  1:47 ` [Patch net 3/3] net_sched: fix two more memory leaks " Cong Wang

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='CAM_iQpV=M18jeWfpFij=TT5YUnwzhyh8POkDx-diRB8BzefyuA@mail.gmail.com' \
    --to=xiyou.wangcong@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=netdev@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).