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]
Date:   Fri, 7 Apr 2017 11:37:07 -0700
From:   Ben Greear <greearb@...delatech.com>
To:     Johannes Berg <johannes@...solutions.net>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Cc:     pablo@...filter.org, Johannes Berg <johannes.berg@...el.com>
Subject: Re: [RFC 2/3] genetlink: pass extended error report down

On 04/07/2017 11:26 AM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@...el.com>
>
> Signed-off-by: Johannes Berg <johannes.berg@...el.com>
> ---
>  include/net/genetlink.h | 27 +++++++++++++++++++++++++++
>  net/netlink/genetlink.c |  6 ++++--
>  2 files changed, 31 insertions(+), 2 deletions(-)
>
> diff --git a/include/net/genetlink.h b/include/net/genetlink.h
> index a34275be3600..67ad2326cfa6 100644
> --- a/include/net/genetlink.h
> +++ b/include/net/genetlink.h
> @@ -84,6 +84,7 @@ struct nlattr **genl_family_attrbuf(const struct genl_family *family);
>   * @attrs: netlink attributes
>   * @_net: network namespace
>   * @user_ptr: user pointers
> + * @exterr: extended error report struct
>   */
>  struct genl_info {
>  	u32			snd_seq;
> @@ -94,6 +95,7 @@ struct genl_info {
>  	struct nlattr **	attrs;
>  	possible_net_t		_net;
>  	void *			user_ptr[2];
> +	struct netlink_ext_err *exterr;
>  };
>
>  static inline struct net *genl_info_net(struct genl_info *info)
> @@ -106,6 +108,31 @@ static inline void genl_info_net_set(struct genl_info *info, struct net *net)
>  	write_pnet(&info->_net, net);
>  }
>
> +static inline int genl_err_str(struct genl_info *info, int err,
> +			       const char *msg)
> +{
> +	info->exterr->msg = msg;
> +
> +	return err;
> +}

I guess the error string must be constant and always available in memory
in this implementation?

I think it would be nice to dynamically create strings (malloc, snprintf, etc)
and have the err_str logic free it when done?

Thanks,
Ben

-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ