public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tristan Lelong <tristan@lelong.xyz>
To: oleg.drokin@intel.com, andreas.dilger@intel.com,
	gregkh@linuxfoundation.org, askb23@gmail.com,
	john.hammond@intel.com, gdonald@gmail.com, anhlq2110@gmail.com,
	fabio.falzoi84@gmail.com, oort10@gmail.com, agimenez@sysvalve.es,
	rupran@einserver.de, surya.seetharaman9@gmail.com,
	Julia.Lawall@lip6.fr, joe@perches.com, a.terekhov@gmail.com,
	liang.zhen@intel.com, vthakkar1994@gmail.com, amk@cray.com,
	srikrishanmalik@gmail.com, rd@radekdostal.com,
	bergwolf@gmail.com, dan.carpenter@oracle.com,
	paul.gortmaker@windriver.com, tapaswenipathak@gmail.com,
	email@christophjaeger.info, uja.ornl@gmail.com,
	brilliantov@inbox.ru, dmitry.eremin@intel.com
Cc: HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros
Date: Wed, 24 Dec 2014 14:53:47 +0100	[thread overview]
Message-ID: <20141224135346.GA6304@lenderer> (raw)
In-Reply-To: <1417910602-20953-1-git-send-email-tristan@lelong.xyz>

On Sat, Dec 06, 2014 at 04:03:22PM -0800, Tristan Lelong wrote:
> This patch fix a sparse warning in lustre sources
> 
> warning: incorrect type in argument 1 (different address spaces)
>     expected void [noderef] <asn:1>*to
>     got char *<noident>
> 
> This is done by adding the missing __user attribute on userland pointers inside the LPROC_SEQ_FOPS like macros:
> - LPROC_SEQ_FOPS
> - LPROC_SEQ_FOPS_RW_TYPE
> - LPROC_SEQ_FOPS_WR_ONLY
> - LDLM_POOL_PROC_WRITER
> 
> The patch also updates all the functions that are used by this macro:
> - lprocfs_wr_*
> - *_seq_write
> 
> as well as some helpers used by the previously modified functions (otherwise fixing the sparse warning add some new ones):
> - lprocfs_write_frac_helper
> - lprocfs_write_helper
> - lprocfs_write_u64_helper
> 
> The patch also fixes one __user pointer direct dereference by strncmp in function fld_proc_hash_seq_write.
> 
> Signed-off-by: Tristan Lelong <tristan@lelong.xyz>
> ---
> Changes in v2:
>         Use dynamic allocation for 'name' variable instead of having it on the stack, per Greg K-H suggestion.
> 
> Changes in v3:
> 	Rename added variable from 'name' to 'fh_name'.
> 	Revert to a stack declaration of 'fh_name' since it is not 80 bytes but only 8, per Andreas Dilger comment.

Hi,

I just wanted to follow up on that patch to see if anybody had any comment.

Thanks

Regards

  reply	other threads:[~2014-12-24 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07  0:03 [PATCH v3] staging: lustre: fix sparse warning on LPROC_SEQ_FOPS macros Tristan Lelong
2014-12-24 13:53 ` Tristan Lelong [this message]
2015-01-17 23:28 ` Greg KH
2015-01-18  6:41   ` Tristan Lelong
2015-01-18  7:02     ` Greg KH
2015-01-20  7:54       ` Tristan Lelong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141224135346.GA6304@lenderer \
    --to=tristan@lelong.xyz \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=Julia.Lawall@lip6.fr \
    --cc=a.terekhov@gmail.com \
    --cc=agimenez@sysvalve.es \
    --cc=amk@cray.com \
    --cc=andreas.dilger@intel.com \
    --cc=anhlq2110@gmail.com \
    --cc=askb23@gmail.com \
    --cc=bergwolf@gmail.com \
    --cc=brilliantov@inbox.ru \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry.eremin@intel.com \
    --cc=email@christophjaeger.info \
    --cc=fabio.falzoi84@gmail.com \
    --cc=gdonald@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=john.hammond@intel.com \
    --cc=liang.zhen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=oort10@gmail.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=rd@radekdostal.com \
    --cc=rupran@einserver.de \
    --cc=srikrishanmalik@gmail.com \
    --cc=surya.seetharaman9@gmail.com \
    --cc=tapaswenipathak@gmail.com \
    --cc=uja.ornl@gmail.com \
    --cc=vthakkar1994@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox