[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.20.1612071950340.1427@casper.infradead.org>
Date: Wed, 7 Dec 2016 19:52:39 +0000 (GMT)
From: James Simmons <jsimmons@...radead.org>
To: Dan Carpenter <dan.carpenter@...cle.com>
cc: Quentin Lambert <lambert.quentin@...il.com>,
devel@...verdev.osuosl.org,
Andreas Dilger <andreas.dilger@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org,
Oleg Drokin <oleg.drokin@...el.com>,
lustre-devel@...ts.lustre.org
Subject: Re: [lustre-devel] [PATCH] staging: lustre: Fix a spatch warning
due to an assignment from kernel to user space
> > 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.
Powered by blists - more mailing lists