netdev - Re: [PATCH] net: switchdev: restrict vid range abstraction

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:	Wed, 29 Jul 2015 12:28:50 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	vivien.didelot@...oirfairelinux.com
Cc:	sfeldma@...il.com, netdev@...r.kernel.org, jiri@...nulli.us,
	f.fainelli@...il.com, linux-kernel@...r.kernel.org,
	kernel@...oirfairelinux.com
Subject: Re: [PATCH] net: switchdev: restrict vid range abstraction

From: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Date: Wed, 29 Jul 2015 15:14:05 -0400 (EDT)

> While a range might be convenient to a user, exposing it to drivers is
> likely to end up writing the same vid_begin to vid_end for loop.

It is impossible not to expose this to the driver.

We have to have a prepare/commit sequence where the prepare part
can see the whole of the request.

It must know the full set of changes it must be able to support
in one go in order to signal a failure properly.

So in fact this is the most convenient way for the drivers to be
exposed to this issue.
--
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