Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932804AbcLGTxP (ORCPT ); Wed, 7 Dec 2016 14:53:15 -0500 Received: from casper.infradead.org ([85.118.1.10]:44854 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753177AbcLGTxA (ORCPT ); Wed, 7 Dec 2016 14:53:00 -0500 Date: Wed, 7 Dec 2016 19:52:39 +0000 (GMT) From: James Simmons To: Dan Carpenter cc: Quentin Lambert , devel@driverdev.osuosl.org, Andreas Dilger , Greg Kroah-Hartman , kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org, Oleg Drokin , lustre-devel@lists.lustre.org Subject: Re: [lustre-devel] [PATCH] staging: lustre: Fix a spatch warning due to an assignment from kernel to user space In-Reply-To: <20161207192237.GP8176@mwanda> Message-ID: References: <20161202173332.5100-1-lambert.quentin@gmail.com> <306D1D4D-A949-44F6-BAFE-44F08F609D9B@intel.com> <81821426-c32c-c45a-e9a3-82f9818fc986@gmail.com> <33d23121-e5ca-0e14-bfbb-632f883e0948@gmail.com> <20161207153317.GO8176@mwanda> <46ee428d-016f-e532-9824-4ddbe8a0cc8b@gmail.com> <20161207192237.GP8176@mwanda> User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20161207_195239_886528_5BA8646A X-CRM114-Status: GOOD ( 15.49 ) X-Spam-Score: -1.9 (-) X-Spam-Report: SpamAssassin version 3.4.1 on casper.infradead.org summary: Content analysis details: (-1.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 NO_RELAYS Informational: message was not relayed via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 847 Lines: 20 > > On 12/07/2016 04:33 PM, Dan Carpenter wrote: > > >Lustre is kind of a mess with regards to keeping user and kernel > > >pointers separate. It's not going to be easy to fix. > > Fair enough. > > I am trying to make a contribution to drivers/staging using sparse. > > With that in mind, do you still fill I should keep clear of lustre? > > I feel that actually doing the work properly could be a meaningful > > learning experience. > > It's just that you're the fifth person to look at lustre __user > annotations and it doesn't end well. You need to be a lustre expert > who can test things. > > But for other lustre things, feel free. Actually we are working to fix this issue. We are working on a process that lustre patch posted here get sucked up and put into our test harness automatically. It needs more love but its coming along.