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:   Thu, 22 Apr 2021 17:28:06 -0600
From:   subashab@...eaurora.org
To:     Alex Elder <elder@...aro.org>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Sean Tranchetti <stranche@...eaurora.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, Daniele Palmas <dnlplm@...il.com>,
        Aleksander Morgado <aleksander@...ksander.es>,
        Loic Poulain <loic.poulain@...aro.org>
Subject: Re: [PATCH] net: qualcomm: rmnet: Allow partial updates of IFLA_FLAGS

On 2021-04-22 12:29, Alex Elder wrote:
> On 4/22/21 1:20 PM, Bjorn Andersson wrote:
>> The idiomatic way to handle the changelink flags/mask pair seems to be
>> allow partial updates of the driver's link flags. In contrast the 
>> rmnet
>> driver masks the incoming flags and then use that as the new flags.
>> 
>> Change the rmnet driver to follow the common scheme, before the
>> introduction of IFLA_RMNET_FLAGS handling in iproute2 et al.
> 
> I like this a lot.  It should have been implemented this way
> to begin with; there's not much point to have the mask if
> it's only applied to the passed-in value.
> 
> KS, are you aware of *any* existing user space code that
> would not work correctly if this were accepted?
> 
> I.e., the way it was (is), the value passed in *assigns*
> the data format flags.  But with Bjorn's changes, the
> data format flags would be *updated* (i.e., any bits not
> set in the mask field would remain with their previous
> value).
> 
> Reviewed-by: Alex Elder <elder@...aro.org>

What rmnet functionality which was broken without this change.
That doesnt seem to be listed in this patch commit text.

If this is an enhancement, then patch needs to be targeted to net-next
instead of net

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ