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
| ||
|
Message-ID: <20230227120420.152a9b32@kernel.org> Date: Mon, 27 Feb 2023 12:04:20 -0800 From: Jakub Kicinski <kuba@...nel.org> To: Jamal Hadi Salim <jhs@...atatu.com> Cc: Simon Horman <simon.horman@...igine.com>, Pedro Tammela <pctammela@...atatu.com>, netdev@...r.kernel.org, xiyou.wangcong@...il.com, jiri@...nulli.us, davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com, amir@...ai.me, dcaratti@...hat.com, willemb@...gle.com, ozsh@...dia.com, paulb@...dia.com Subject: Re: [PATCH net 1/3] net/sched: act_pedit: fix action bind logic On Mon, 27 Feb 2023 14:51:58 -0500 Jamal Hadi Salim wrote: > > > I agree that shouldn't be the case. > > > For me that doesn't make it a bug, but I don't feel strongly about it. > > > > I'm with Simon - this is a long standing problem, and we weren't getting > > any user complaints about this. So I also prefer to route this via > > net-next, without the Fixes tags. > > At minimum the pedit is a fix. How come? What makes pedit different? It's kinda hard to parse from the diff and the commit messages look copy/pasted. > The rest is toss-a-coin and put in net-next or net.
Powered by blists - more mailing lists