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:   Mon, 11 Apr 2022 18:49:11 +0300
From:   Vladimir Oltean <>
To:     Nicolas Dichtel <>
Cc:     Jakub Kicinski <>,,
        "David S. Miller" <>,
        Paolo Abeni <>
Subject: Re: What is the purpose of dev->gflags?

On Mon, Apr 11, 2022 at 05:43:01PM +0200, Nicolas Dichtel wrote:
> Le 11/04/2022 à 17:33, Vladimir Oltean a écrit :
> [snip]
> > Would you agree that the __dev_set_allmulti() -> __dev_notify_flags()
> > call path is dead code? If it is, is there any problem it should be
> > addressing which it isn't, or can we just delete it?
> I probably miss your point, why is it dead code?

Because __dev_set_allmulti() doesn't update dev->gflags, it means
dev->gflags == old_gflags. In turn, it means dev->gflags ^ old_gflags,
passed to "gchanges" of __dev_notify_flags(), is 0.

Powered by blists - more mailing lists