linux-kernel - Re: [PATCH] net: drop_monitor: use IS_REACHABLE() to guard net_dm_hw

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: <20200311104756.GA1972672@hmswarspite.think-freely.org>
Date:   Wed, 11 Mar 2020 06:47:56 -0400
From:   Neil Horman <nhorman@...driver.com>
To:     Ido Schimmel <idosch@...lanox.com>
Cc:     Masahiro Yamada <masahiroy@...nel.org>, jiri@...lanox.com,
        netdev@...r.kernel.org, "David S . Miller" <davem@...emloft.net>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Nicolas Pitre <nico@...xnic.net>, linux-kbuild@...r.kernel.org,
        Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: drop_monitor: use IS_REACHABLE() to guard
 net_dm_hw_report()

On Wed, Mar 11, 2020 at 11:31:43AM +0200, Ido Schimmel wrote:
> On Wed, Mar 11, 2020 at 03:29:25PM +0900, Masahiro Yamada wrote:
> > In net/Kconfig, NET_DEVLINK implies NET_DROP_MONITOR.
> > 
> > The original behavior of the 'imply' keyword prevents NET_DROP_MONITOR
> > from being 'm' when NET_DEVLINK=y.
> > 
> > With the planned Kconfig change that relaxes the 'imply', the
> > combination of NET_DEVLINK=y and NET_DROP_MONITOR=m would be allowed.
> > 
> > Use IS_REACHABLE() to avoid the vmlinux link error for this case.
> > 
> > Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> > Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
> 
> Thanks, Masahiro.
> 
> Neil, Jiri, another option (long term) is to add a raw tracepoint (not
> part of ABI) in devlink and have drop monitor register its probe on it
> when monitoring.
> 
> Two advantages:
> 1. Consistent with what drop monitor is already doing with kfree_skb()
> tracepoint
> 2. We can remove 'imply NET_DROP_MONITOR' altogether
> 
> What do you think?
> 
Agreed, I think I like this implementation better.
Neil