public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	amirv-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
	Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Dan Carpenter
	<dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH for-next 3/6] IB/core: Avoid leakage from kernel to user space
Date: Mon, 15 Sep 2014 15:45:00 +0200	[thread overview]
Message-ID: <1410788700.7830.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1410702475-28826-4-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Hi,

Le dimanche 14 septembre 2014 à 16:47 +0300, Eli Cohen a écrit :
> Clear the reserved field of struct ib_uverbs_async_event_desc which is 
> copied to user space.
> 

This one could be applied right now on v3.17 and others.

> Signed-off-by: Eli Cohen <eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

Reviewed-by: Yann Droneaud <ydroneaud-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
Cc: stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org

Regards.

> ---
>  drivers/infiniband/core/uverbs_main.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/infiniband/core/uverbs_main.c b/drivers/infiniband/core/uverbs_main.c
> index c73b22a257fe..b21af1eaf503 100644
> --- a/drivers/infiniband/core/uverbs_main.c
> +++ b/drivers/infiniband/core/uverbs_main.c
> @@ -477,6 +477,7 @@ static void ib_uverbs_async_handler(struct ib_uverbs_file *file,
>  
>  	entry->desc.async.element    = element;
>  	entry->desc.async.event_type = event;
> +	entry->desc.async.reserved   = 0;
>  	entry->counter               = counter;
>  
>  	list_add_tail(&entry->list, &file->async_file->event_list);


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-09-15 13:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-14 13:47 [PATCH for-next 0/6] minor mlx5 fixes for 3.18 Eli Cohen
     [not found] ` <1410702475-28826-1-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-09-14 13:47   ` [PATCH for-next 1/6] IB/mlx5: Clear umr resources after ib_unregister_device Eli Cohen
2014-09-14 13:47   ` [PATCH for-next 2/6] IB/mlx5: Improve debug prints in mlx5_ib_reg_user_mr Eli Cohen
2014-09-14 13:47   ` [PATCH for-next 3/6] IB/core: Avoid leakage from kernel to user space Eli Cohen
     [not found]     ` <1410702475-28826-4-git-send-email-eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-09-15 13:45       ` Yann Droneaud [this message]
2015-03-27 12:42         ` [-stable] commit 377b513485fd ("IB/core: Avoid leakage from kernel to user space") Yann Droneaud
     [not found]           ` <1427460164.12712.8.camel-RlY5vtjFyJ3QT0dZR+AlfA@public.gmane.org>
2015-03-30 10:21             ` Luis Henriques
2015-03-31  9:49           ` Jiri Slaby
2015-05-04 23:04           ` Ben Hutchings
2015-06-15  3:31           ` Zefan Li
2014-09-14 13:47   ` [PATCH for-next 4/6] IB/mlx5: Fix possible array overflow Eli Cohen
2014-09-14 13:47   ` [PATCH for-next 5/6] IB/mlx5: Remove duplicate code from mlx5_set_path Eli Cohen
2014-09-14 13:47   ` [PATCH for-next 6/6] IB/mlx5: Modify to work with arbitrary page size Eli Cohen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1410788700.7830.3.camel@localhost.localdomain \
    --to=ydroneaud-rly5vtjfyj3qt0dzr+alfa@public.gmane.org \
    --cc=amirv-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=eli-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox