[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5b38692a40561b983f379a2d19de238f444fe50f.camel@codeconstruct.com.au>
Date: Fri, 05 Nov 2021 08:23:01 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Eugene Syromiatnikov <esyr@...hat.com>,
Matt Johnston <matt@...econstruct.com.au>
Cc: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/2] MCTP sockaddr padding
check/initialisation fixup
Hi Eugene,
> While the first commit is definitely an ABI breakage, it is proposed
> in hopes that the change is made soon enough (the interface appeared
> only in Linux 5.15) to avoid affecting any existing user space.
Of the two applications that currently use AF_MCTP:
- one is already zeroing the sockaddr_mctp
- the other has a fix for two of the potential sendmsg() & bind()
calls: https://github.com/CodeConstruct/mctp/commit/072bafe7
Given we have a confined set of applications (and users), and they're
both now compatible with this change:
Acked-by: Jeremy Kerr <jk@...econstruct.com.au>
For both patches.
Cheers,
Jeremy
Powered by blists - more mailing lists