All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
	jeyu@kernel.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com,
	brueckner@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
	peterz@infradead.org, me@tobin.cc, keescook@chromium.org
Subject: Re: [PATCH] modules: Fix display of wrong module .text address
Date: Tue, 17 Apr 2018 13:20:00 -0300	[thread overview]
Message-ID: <20180417162000.GA7157@kernel.org> (raw)
In-Reply-To: <a967eb54-9c54-f9a7-f92a-0ae3d8eb60ba@de.ibm.com>

Em Tue, Apr 17, 2018 at 10:24:35AM +0200, Christian Borntraeger escreveu:
> 
> 
> On 04/17/2018 10:20 AM, Thomas Richter wrote:
> > In kernel v4.16.0 the module .text address is displayed
> > wrong when using /sys/module/*/sections/.text file.
> > Commit ef0010a30935 ("vsprintf: don't use 'restricted_pointer()' when
> > not restricting")
> > is the first bad commit.
> > 
> > Here is the issue, using module qeth_l2 on s390 which is the
> > ethernet device driver:
> > 
> > [root@s35lp76 ~]# lsmod
> > Module                  Size  Used by
> > qeth_l2                94208  1
> > ...
> > 
> > [root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
> > qeth_l2 94208 1 - Live 0x000003ff80401000
> >                        ^ This is the correct address in memory
> > [root@s35lp76 ~]# cat /sys/module/qeth_l2/sections/.text
> > 0x0000000018ea8363      <---- This is a wrong address
> > [root@s35lp76 ~]#
> > 
> > This breaks the perf tool which uses this address on s390
> > to calculate start of .text section in memory.
> > 
> > Fix this by printing the correct (unhashed) address.
> > 
> > Thanks to Jessica Yu for helping on this.
> > 
> > Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> > Cc: Jessica Yu <jeyu@kernel.org>
> 
> CC stable?

Adding the missing:

Fixes: ef0010a30935 ("vsprintf: don't use 'restricted_pointer()' when not restricting")

Should be enough?

- Arnaldo
 
> > ---
> >  kernel/module.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/kernel/module.c b/kernel/module.c
> > index a6e43a5806a1..77ab7211ddef 100644
> > --- a/kernel/module.c
> > +++ b/kernel/module.c
> > @@ -1472,7 +1472,7 @@ static ssize_t module_sect_show(struct module_attribute *mattr,
> >  {
> >  	struct module_sect_attr *sattr =
> >  		container_of(mattr, struct module_sect_attr, mattr);
> > -	return sprintf(buf, "0x%pK\n", (void *)sattr->address);
> > +	return sprintf(buf, "%#lx\n", kptr_restrict < 2 ? sattr->address : 0);
> >  }
> >  
> >  static void free_sect_attrs(struct module_sect_attrs *sect_attrs)
> > 

  parent reply	other threads:[~2018-04-17 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  8:20 [PATCH] modules: Fix display of wrong module .text address Thomas Richter
2018-04-17  8:24 ` Christian Borntraeger
2018-04-17 16:10   ` Kees Cook
2018-04-17 16:20   ` Arnaldo Carvalho de Melo [this message]
2018-04-17 17:34     ` Christian Borntraeger

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=20180417162000.GA7157@kernel.org \
    --to=acme@kernel.org \
    --cc=borntraeger@de.ibm.com \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jeyu@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=peterz@infradead.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tmricht@linux.ibm.com \
    --cc=torvalds@linux-foundation.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.