netdev - Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking option

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]

Date:	Fri, 16 Oct 2015 10:09:25 +0200
From:	Thomas Graf <tgraf@...g.ch>
To:	Jiri Benc <jbenc@...hat.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [RFC PATCH net-next 0/9] netlink: strict attribute checking
 option

On 10/16/15 at 10:02am, Jiri Benc wrote:
> On Fri, 16 Oct 2015 01:06:44 -0700 (PDT), David Miller wrote:
> > No, it's definitely not OK, because lwtunnel support exists in
> > Linus's tree.
> > 
> > And tools should be able to work on all kernels where lwtunnel support
> > is available.
> 
> You can consider the lwtunnels feature as not finished in the current
> Linus's tree. It works, it won't change (thus anything using it in its
> current form will continue to work in all the future kernels), but
> mainstream tools won't make use of it until a kernel version later
> which will get some additional support.
> 
> I don't think it's much of a problem and I don't think it is the first
> time this would happen.
> 
> I'm afraid I don't have any solution that could do better.

Maybe we should be more precise here. The detection mechanism is only
for tools which want to know whether lwt or another feature is supported
without going through the pain of creating an object, checking its
attributes and then deleting the object again if no full support was
detected. The existing flow of configuration through iproute2 will be
supported just like for any other new feature that we have introduced.

Therefore, I consider this a future optimization.

This is very much related to the offload problematic we had or still
have of "only program in HW if you can do the full thing vs best effort"
so this flag will be of use in a wider context.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html