netdev - Re: [Patch net-next] net_sched: properly handle failure case of tcf_exts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM_iQpVJt9fE_anNXq=Jvi_Ka=BtN-_H365+oEBpFrxJv6dU3A@mail.gmail.com>
Date:   Mon, 22 Aug 2016 10:40:50 -0700
From:   Cong Wang <xiyou.wangcong@...il.com>
To:     Jamal Hadi Salim <jhs@...atatu.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [Patch net-next] net_sched: properly handle failure case of tcf_exts_init()

On Mon, Aug 22, 2016 at 5:11 AM, Jamal Hadi Salim <jhs@...atatu.com> wrote:
>
>
> Answered my own question by looking at implementation of kfree();
> ignores NULL (unlike free())

Seriously?

Here is what C standard says about free():

The free function causes the space pointed to by ptr to be
deallocated, that is, made available for further allocation. If ptr is
a null pointer, no action occurs.