From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [Patch v2 3/4] tools/xenstored: Avoid buffer overflows while setting up sockets [and 1 more messages] Date: Fri, 13 Dec 2013 19:15:04 +0000 Message-ID: <52AB5CB8.7080604@citrix.com> References: <1385390321-10124-1-git-send-email-andrew.cooper3@citrix.com> <529C88AC.5070706@citrix.com> <52A5C659.4040902@citrix.com> <52AB4E44.9060309@citrix.com> <21163.20920.529172.797714@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <21163.20920.529172.797714@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: Matthew Daley , Ian Campbell , Xen-devel List-Id: xen-devel@lists.xenproject.org On 13/12/2013 18:28, Ian Jackson wrote: > Andrew Cooper writes ("[Xen-devel] [Patch v2 3/4] tools/xenstored: Avoid buffer overflows while setting up sockets"): >> Coverity ID: 1055996 1056002 >> >> Cache the xs_daemon_socket{,_ro}() strings to save pointlessly >> re-snprintf()'ing the same path, and add explicit size checks against >> addr.sun_path before strcpy()'ing into it. >> >> Signed-off-by: Andrew Cooper >> CC: Ian Campbell >> CC: Ian Jackson >> CC: Matthew Daley > Acked-by: Ian Jackson > Committed-by: Ian Jackson > > Andrew Cooper writes ("Re: [Xen-devel] [Patch v2 3/4] tools/xenstored: Avoid buffer overflows while setting up sockets"): >> Given the spirit today of missed pings on patches, >> >> Third time lucky? > Sorry about that. (Coverity is generating a lot of very similar > patches; in this case I had confused this one in my mind with > f220279c14 which you even mention in the commit message.) > > Thanks for chasing. > > Ian. Yes - that is a sad fact of all of these similar patches. Hopefully they will start thinning out as we get on top of the issues. I am tracking "what still hasn't been applied" by what `git rebase staging` tells me has still is still outstanding. Of course, being my private working tree, it is not easily exportable information. On that note, I have some more pings to go. ~Andrew