linux-kernel - RE: [PATCH net-next] hyper-v: make uuid

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <04f86b9536044961bb702ecf554fc146@BL2PR03MB291.namprd03.prod.outlook.com>
Date:	Tue, 3 Jun 2014 17:30:28 +0000
From:	KY Srinivasan <kys@...rosoft.com>
To:	Stephen Hemminger <stephen@...workplumber.org>,
	Haiyang Zhang <haiyangz@...rosoft.com>
CC:	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next] hyper-v: make uuid_le const



> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@...workplumber.org]
> Sent: Tuesday, June 3, 2014 8:38 AM
> To: KY Srinivasan; Haiyang Zhang
> Cc: devel@...uxdriverproject.org; linux-kernel@...r.kernel.org;
> netdev@...r.kernel.org
> Subject: [PATCH net-next] hyper-v: make uuid_le const
> 
> The uuid structure could be managed as a const in several places.
> 
> Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>

Thanks Stephen.

Signed-off-by: K. Y. Srinivasan <kys@...rosoft.com>

> 
> ---
> Patch against net-next because that is where most recent hyper-v related
> changes are.
> 
> 
> --- a/drivers/hv/channel_mgmt.c	2014-02-12 08:21:54.627887619 -0800
> +++ b/drivers/hv/channel_mgmt.c	2014-06-03 08:08:47.030901345 -0700
> @@ -365,7 +365,7 @@ static u32  next_vp;
>   * performance critical channels (IDE, SCSI and Network) will be uniformly
>   * distributed across all available CPUs.
>   */
> -static u32 get_vp_index(uuid_le *type_guid)
> +static u32 get_vp_index(const uuid_le *type_guid)
>  {
>  	u32 cur_cpu;
>  	int i;
> --- a/drivers/hv/vmbus_drv.c	2014-04-07 11:21:05.704486433 -0700
> +++ b/drivers/hv/vmbus_drv.c	2014-06-03 08:11:14.771854064 -0700
> @@ -435,7 +435,7 @@ static int vmbus_uevent(struct device *d
>  	return ret;
>  }
> 
> -static uuid_le null_guid;
> +static const uuid_le null_guid;
> 
>  static inline bool is_null_guid(const __u8 *guid)  { @@ -450,7 +450,7 @@
> static inline bool is_null_guid(const __
>   */
>  static const struct hv_vmbus_device_id *hv_vmbus_get_id(
>  					const struct hv_vmbus_device_id
> *id,
> -					__u8 *guid)
> +					const __u8 *guid)
>  {
>  	for (; !is_null_guid(id->guid); id++)
>  		if (!memcmp(&id->guid, guid, sizeof(uuid_le))) @@ -779,9
> +779,9 @@ EXPORT_SYMBOL_GPL(vmbus_driver_unregiste
>   * vmbus_device_create - Creates and registers a new child device
>   * on the vmbus.
>   */
> -struct hv_device *vmbus_device_create(uuid_le *type,
> -					    uuid_le *instance,
> -					    struct vmbus_channel *channel)
> +struct hv_device *vmbus_device_create(const uuid_le *type,
> +				      const uuid_le *instance,
> +				      struct vmbus_channel *channel)
>  {
>  	struct hv_device *child_device_obj;
> 
> --- a/drivers/hv/hyperv_vmbus.h	2014-04-07 11:21:05.704486433 -0700
> +++ b/drivers/hv/hyperv_vmbus.h	2014-06-03 08:27:12.618223800 -0700
> @@ -644,9 +644,9 @@ extern struct vmbus_connection vmbus_con
> 
>  /* General vmbus interface */
> 
> -struct hv_device *vmbus_device_create(uuid_le *type,
> -					 uuid_le *instance,
> -					 struct vmbus_channel *channel);
> +struct hv_device *vmbus_device_create(const uuid_le *type,
> +				      const uuid_le *instance,
> +				      struct vmbus_channel *channel);
> 
>  int vmbus_device_register(struct hv_device *child_device_obj);  void
> vmbus_device_unregister(struct hv_device *device_obj);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/