[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1465507031.7945.44.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Thu, 09 Jun 2016 14:17:11 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Saeed Mahameed <saeedm@...lanox.com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org,
Yevgeny Petrilin <yevgenyp@...lanox.com>,
Andre Melkoumian <andre@...lanox.com>,
Matthew Finlay <matt@...lanox.com>,
Pablo Neira Ayuso <pablo@...filter.org>,
Patrick McHardy <kaber@...sh.net>,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>
Subject: Re: [PATCH net-next] nfnetlink_queue: enable PID info retrieval
On Thu, 2016-06-09 at 23:50 +0300, Saeed Mahameed wrote:
> From: Matthew Finlay <matt@...lanox.com>
> diff --git a/net/socket.c b/net/socket.c
> index a1bd161..67de200 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -382,6 +382,7 @@ struct file *sock_alloc_file(struct socket *sock, int flags, const char *dname)
> }
>
> sock->file = file;
> + file->f_owner.sock_pid = find_get_pid(task_pid_nr(current));
> file->f_flags = O_RDWR | (flags & O_NONBLOCK);
> file->private_data = sock;
> return file;
Wow, that is a serious memory leak weapon (of struct pid)
Why don't you store the pid value, instead of a pointer ?
Powered by blists - more mailing lists