From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp2130.oracle.com ([141.146.126.79]:40294 "EHLO aserp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728458AbeHNRkB (ORCPT ); Tue, 14 Aug 2018 13:40:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=corp-2018-07-02; bh=yzTipUxqutFUkj5Eqo9NJ2ACfik7rL+6VWjjE0uYOug=; b=rK+O0ntetZVVfJ+9Fwlyv1/64yFsUwbUck6HMVc18n79quvdSDK74YTdHoYXv+AIglcO VL2zPRfAYDVOrQLEbAWWpwujYeadCUF/K8biF8rCYD/BEAZl++Iordg3IWPC1++YNmN6 KrzoK0DkuP7rxBWuiknIitaW+lhGmw3nOrEM9rshGfRsQb1c3f7ALUNAjx4zsEvxibaA z73dI0+1BL6mGPYRbQ3SUbvFZTg1kKGhBkzJrmmXeEOfN97OYQElqG8ErF7suOp+a3NP zffQeK1EbD2lRPcMmS9mOwZQGAMzED3aNywUVv2qmDDCi2oQRNYJGqyGa4kNSs5WOCTC QQ== Date: Tue, 14 Aug 2018 17:52:20 +0300 From: Dan Carpenter Subject: Re: Smatch for Xen Message-ID: <20180814145220.uzmcdwh3guqeb2kh@mwanda> References: <20180806112003.iyir4napbpn4q6z6@mwanda> <20180806131632.w4rd3ntfgoxwxb5l@mwanda> <20180806135409.r5xytcrffqi3ddco@mwanda> <20180813175845.muweaoh6s5rxcr57@mwanda> <20180813183132.suxab5gfub5uig2k@mwanda> <20180814142117.v7tavkwisxcoel2f@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: smatch-owner@vger.kernel.org List-ID: To: Norbert Manthey Cc: Norbert Manthey , smatch@vger.kernel.org, jsteckli@amazon.com, tautschn@amazon.co.uk On Tue, Aug 14, 2018 at 04:33:15PM +0200, Norbert Manthey wrote: > Oh, that's nice. I'll play with the new script. > > Concerning the copy from user functions, I have a few patches locally to > get the functions into the tool, which I just have to make a little > nicer before sharing. I will post them once done. Forget about making it nice. Just send it. :) > I found the > "copy_from_guest" string also at other places, as well as matching > syscalls which come with a user controllable argument. The patches > should cover all those. In the kernel, syscalls should be covered. Historically, it does matter how the kernel is configured, but hopefully we've fixed those bugs. Also we keep changing the SYS_CALL macros, so I can't swear that all versions work. regars, dan carpenter