public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, avagin@virtuozzo.com,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH v2] proc: fix /proc/*/map_files lookup some more
Date: Wed, 21 Feb 2018 23:58:55 +0300	[thread overview]
Message-ID: <20180221205855.GA2540@avx2> (raw)
In-Reply-To: <20180221120403.504b7f1c814618bac39bb78b@linux-foundation.org>

On Wed, Feb 21, 2018 at 12:04:03PM -0800, Andrew Morton wrote:
> On Wed, 21 Feb 2018 22:53:40 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> 
> > I totally forgot that _parse_integer() accepts arbitrary amount of
> > leading zeroes leading to the following:
> > 
> > 		OK
> > 	# readlink /proc/1/map_files/56427ecba000-56427eddc000
> > 	/lib/systemd/systemd
> > 
> > 		bogus
> > 	# readlink /proc/1/map_files/00000000000056427ecba000-56427eddc000
> > 	/lib/systemd/systemd
> > 	# readlink /proc/1/map_files/56427ecba000-00000000000056427eddc000
> > 	/lib/systemd/systemd
> > 
> > ...
> > 
> > --- a/fs/proc/base.c
> > +++ b/fs/proc/base.c
> > @@ -1916,6 +1916,8 @@ static int dname_to_vma_addr(struct dentry *dentry,
> >  	unsigned long long sval, eval;
> >  	unsigned int len;
> >  
> > +	if (str[0] == '0' && str[1])
> > +		return -EINVAL;
> >  	len = _parse_integer(str, 16, &sval);
> >  	if (len & KSTRTOX_OVERFLOW)
> >  		return -EINVAL;
> > @@ -1927,6 +1929,8 @@ static int dname_to_vma_addr(struct dentry *dentry,
> >  		return -EINVAL;
> >  	str++;
> >  
> > +	if (str[0] == '0' && str[1])
> > +		return -EINVAL;
> >  	len = _parse_integer(str, 16, &eval);
> >  	if (len & KSTRTOX_OVERFLOW)
> >  		return -EINVAL;
> 
> I don't know this code and I'm all confused.
> 
> - why is the code designed to accept addresses of "0"?

Now I'm confused.
Code rejects, say ,'07ff...-...' because printing with %lx-%lx would never
produce leading zero.

> - how do we know that the first digit of a VMA address will never be 0?

Except when address is exactly 0 but this case is handled by looking at
the second character.

  parent reply	other threads:[~2018-02-21 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 18:44 [PATCH] proc: fix /proc/*/map_files lookup some more Alexey Dobriyan
2018-02-21 18:51 ` Al Viro
2018-02-21 19:53   ` [PATCH v2] " Alexey Dobriyan
2018-02-21 20:04     ` Andrew Morton
2018-02-21 20:29       ` Cyrill Gorcunov
2018-02-21 20:58       ` Alexey Dobriyan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-03 21:51 Alexey Dobriyan
2018-03-04 20:53 ` Cyrill Gorcunov

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=20180221205855.GA2540@avx2 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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