netdev - Re: [PATCH net-next 2/4] tools: ynl: user space helpers

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] [day] [month] [year] [list]

Message-ID: <ZH3MVCH766QotC5K@corigine.com>
Date: Mon, 5 Jun 2023 13:51:48 +0200
From: Simon Horman <simon.horman@...igine.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
	pabeni@...hat.com
Subject: Re: [PATCH net-next 2/4] tools: ynl: user space helpers

On Sun, Jun 04, 2023 at 11:00:34AM -0700, Jakub Kicinski wrote:
> On Sat, 3 Jun 2023 16:47:10 +0200 Simon Horman wrote:
> > > +/**
> > > + * struct ynl_error - error encountered by YNL
> > > + * Users should interact with the err member of struct ynl_sock directly.
> > > + * The main exception to that rule is ynl_sock_create().  
> > 
> > nit: As this is a kernel doc, maybe document the structure members here.
> > 
> > > + */
> > > +struct ynl_error {
> > > +	enum ynl_error_code code;
> > > +	unsigned int attr_offs;
> > > +	char msg[512];
> > > +};
> > > +
> > > +/**
> > > + * struct ynl_family - YNL family info
> > > + * Family description generated by codegen.  
> > 
> > And here.
> > 
> > > + */
> > > +struct ynl_family {
> > > +	const char *name;
> > > +	const struct ynl_ntf_info *ntf_info;
> > > +	unsigned int ntf_info_size;
> > > +};  
> > 
> > ...
> > 
> > > +/**
> > > + * ynl_has_ntf() - check if socket has *parsed* notifications
> > > + * Note that this does not take into account notifications sitting
> > > + * in netlink socket, just the notifications which have already been
> > > + * read and parsed (e.g. during a ynl_ntf_check() call).  
> > 
> > And the parameter of this function here.
> 
> Thanks, not sure why my brain considered this "not really kernel code
> so I don't have to obey the rules" :S I marked the innards of the
> family as private, and tossed in the other descriptions. v2 posted.

Thanks, I assumed it was something like that.