[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140502235616.GJ4963@mwanda>
Date: Sat, 3 May 2014 02:56:16 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Yann Droneaud <ydroneaud@...eya.com>
Cc: Steve Wise <swise@...lsio.com>, Roland Dreier <roland@...nel.org>,
Sean Hefty <sean.hefty@...el.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
linux-rdma@...r.kernel.org, kernel-janitors@...r.kernel.org,
netdev@...r.kernel.org, davem@...emloft.net,
roland@...estorage.com, dm@...lsio.com, leedom@...lsio.com,
santosh@...lsio.com, kumaras@...lsio.com, nirranjan@...lsio.com,
hariprasad@...lsio.com, Steve Wise <swise@...ngridcomputing.com>
Subject: Re: [patch] RDMA/cxgb4: info leak in c4iw_alloc_ucontext()
On Fri, Mar 28, 2014 at 11:27:48AM +0100, Yann Droneaud wrote:
> Unfortunately, it's not the only structure which has this problem. I'm
> currently preparing a report on this issue for this driver (cxgb4) and
> another.
>
This information leak is still present in linux-next. These days we
count those things as security vulnerabilities with CVEs and everything.
When is it likely to get fixed?
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists