Message ID | 20240503082732.2835810-1-steffen.klassert@secunet.com (mailing list archive) |
---|---|
State | Accepted |
Delegated to: | Netdev Maintainers |
Headers | show |
On Fri, May 03, 2024 at 10:27:26AM +0200, Steffen Klassert wrote: > 1) Remove Obsolete UDP_ENCAP_ESPINUDP_NON_IKE Support. > This was defined by an early version of an IETF draft > that did not make it to a standard. > > 2) Introduce direction attribute for xfrm states. > xfrm states have a direction, a stsate can be used > either for input or output packet processing. > Add a direction to xfrm states to make it clear > for what a xfrm state is used. > > All patches from Antony Antony. > > Please pull or let me know if there are problems. Hi Steffen, all, This comment is not strictly related to this pull request and certainly not intended to impede progress of it towards upstream. However, while looking over it I noticed that Sparse flags a rather large number of warnings in xfrm code, mostly relating to __rcu annotations. I'm wondering if, at some point, these could be addressed somehow.
On Sat, May 04, 2024 at 03:36:57PM +0100, Simon Horman wrote: > > Hi Steffen, all, > > This comment is not strictly related to this pull request > and certainly not intended to impede progress of it towards upstream. > > However, while looking over it I noticed that Sparse flags a rather > large number of warnings in xfrm code, mostly relating to __rcu annotations. > I'm wondering if, at some point, these could be addressed somehow. Yes, maybe just start to not introduce new ones and then fix existing ones over time. I'll have a look on how I can integrate Sparse checks in my workflow.
On Tue, May 07, 2024 at 11:00:27AM +0200, Steffen Klassert wrote: > On Sat, May 04, 2024 at 03:36:57PM +0100, Simon Horman wrote: > > > > Hi Steffen, all, > > > > This comment is not strictly related to this pull request > > and certainly not intended to impede progress of it towards upstream. > > > > However, while looking over it I noticed that Sparse flags a rather > > large number of warnings in xfrm code, mostly relating to __rcu annotations. > > I'm wondering if, at some point, these could be addressed somehow. > > Yes, maybe just start to not introduce new ones and then fix > existing ones over time. I'll have a look on how I can integrate > Sparse checks in my workflow. Thanks Steffen, That would be much appreciated.