All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 4/4] NFSD: Ignore and warn once for more fslocs or more uuids
Date: Fri, 23 May 2014 10:41:28 -0400	[thread overview]
Message-ID: <20140523144128.GO25423@fieldses.org> (raw)
In-Reply-To: <537F5A1A.9000005@gmail.com>

On Fri, May 23, 2014 at 10:24:26PM +0800, Kinglong Mee wrote:
> On 5/23/2014 21:54, J. Bruce Fields wrote:
> > On Fri, May 23, 2014 at 08:01:47PM +0800, Kinglong Mee wrote:
> >> If mountd writes more fslocs or more uuids, just ignore and warn once.
> > 
> > So the current behavior is a leak?
> 
> Yes, there is a memory leak for more fslocs or more uuids.
> 
> > 
> > Have you observed any version of mountd actually writing more than one
> > of these?
> 
> Sorry, i don't checkout it.
> I just review the codes, and rewrit nfs-utils to writing more fslocs or uuids.
> 
> > 
> > If not, I'd prefer to return an error.
> 
> You mean return -EINVAL instead of ignoring it with return 0? 

Right.  If somebody introduces weird mountd behavior I'd rather they see
it fail right away.  And also I think it's a little easier to extend
these calls later if we error out on invalid input.

Also, remove the WARN_ON_ONCE.  We usually reserve BUG or WARN for cases
where we believe the kernel itself has a bug, and avoid them in cases
where they could be triggered by userland.  (Admittedly mountd is very
special userland, but still I'd rather it not be able to trigger these.)

--b.

> 
> Although, i miss checking the more "secinfo" in secinfo_parse() right now,
> for no memory leak. I will adds it after decides how to fix above.
> 
> thanks,
> Kinglong Mee
> 
> > 
> > --b.
> > 
> >>
> >> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> >> ---
> >>  fs/nfsd/export.c | 12 ++++++++++++
> >>  1 file changed, 12 insertions(+)
> >>
> >> diff --git a/fs/nfsd/export.c b/fs/nfsd/export.c
> >> index 90d37b6..1d56ae3 100644
> >> --- a/fs/nfsd/export.c
> >> +++ b/fs/nfsd/export.c
> >> @@ -394,6 +394,12 @@ fsloc_parse(char **mesg, char *buf, struct nfsd4_fs_locations *fsloc)
> >>  	int len;
> >>  	int migrated, i, err;
> >>  
> >> +	/* utils writes more fslocs than one */
> >> +	if (fsloc->locations) {
> >> +		WARN_ON_ONCE(1);
> >> +		return 0;
> >> +	}
> >> +
> >>  	/* listsize */
> >>  	err = get_uint(mesg, &fsloc->locations_count);
> >>  	if (err)
> >> @@ -485,6 +491,12 @@ uuid_parse(char **mesg, char *buf, unsigned char **puuid)
> >>  {
> >>  	int len;
> >>  
> >> +	/* utils writes more uuid than one */
> >> +	if (*puuid) {
> >> +		WARN_ON_ONCE(1);
> >> +		return 0;
> >> +	}
> >> +
> >>  	/* expect a 16 byte uuid encoded as \xXXXX... */
> >>  	len = qword_get(mesg, buf, PAGE_SIZE);
> >>  	if (len != EX_UUID_LEN)
> >> -- 
> >> 1.9.0
> >>
> > 

  reply	other threads:[~2014-05-23 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 12:01 [PATCH 4/4] NFSD: Ignore and warn once for more fslocs or more uuids Kinglong Mee
2014-05-23 13:54 ` J. Bruce Fields
2014-05-23 14:24   ` Kinglong Mee
2014-05-23 14:41     ` J. Bruce Fields [this message]
2014-05-24  3:19       ` [PATCH v2] NFSD: Error out when getting more than one fsloc/secinfo/uuid Kinglong Mee
2014-05-27 15:47         ` J. Bruce Fields

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=20140523144128.GO25423@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kinglongmee@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.