netdev - Re: [PATCH v3 net-next] taprio: validate TCA_TAPRIO_ATTR_FLAGS through policy instead of open-coding

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: <cacb4e78-9ec1-437a-9017-9101a3014b8d@gmail.com>
Date: Sun, 28 Jan 2024 17:13:56 +0100
From: Alessandro Marcolini <alessandromarcolini99@...il.com>
To: Simon Horman <horms@...nel.org>
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next] taprio: validate TCA_TAPRIO_ATTR_FLAGS
 through policy instead of open-coding

On 1/26/24 22:14, Simon Horman wrote:
> For reference, and I don't think it's probably not
> necessary to repost because of this, these days
> it is normal to put the Changes below the scissors (---).
> This means they don't end up in the git history.
> But now we have lore that seems to be less of an issue.
Thank you very much! I'll keep this in mind for future patches :)