LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>, Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [BUG] general protection fault when reading /proc/kcore
Date: Mon, 16 Aug 2021 19:54:24 +0200 [thread overview]
Message-ID: <d05f4d38-fdb8-29a6-202e-19d65cd0b1f1@redhat.com> (raw)
In-Reply-To: <1a05d147-e249-7682-2c86-bbd157bc9c7d@redhat.com>
On 16.08.21 19:49, David Hildenbrand wrote:
> On 16.08.21 19:34, Jiri Olsa wrote:
>> hi,
>> I'm getting fault below when running:
>>
>> # cat /proc/kallsyms | grep ksys_read
>> ffffffff8136d580 T ksys_read
>> # objdump -d --start-address=0xffffffff8136d580 --stop-address=0xffffffff8136d590 /proc/kcore
>>
>> /proc/kcore: file format elf64-x86-64
>>
>> Segmentation fault
>>
>> any idea? config is attached
>
> Just tried with a different config on 5.14.0-rc6+
>
> [root@localhost ~]# cat /proc/kallsyms | grep ksys_read
> ffffffff8927a800 T ksys_readahead
> ffffffff89333660 T ksys_read
>
> [root@localhost ~]# objdump -d --start-address=0xffffffff89333660
> --stop-address=0xffffffff89333670
>
> a.out: file format elf64-x86-64
Sorry, missed the /proc/kcore part:
[root@localhost ~]# cat /proc/kallsyms | grep ksys_read
ffffffffba27a800 T ksys_readahead
ffffffffba333660 T ksys_read
[root@localhost ~]# objdump -d --start-address=0xffffffffba333660
--stop-address=0xffffffffba333670 /proc/kcore
/proc/kcore: file format elf64-x86-64
Disassembly of section load1:
ffffffffba333660 <load1+0x333660>:
ffffffffba333660: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
ffffffffba333665: 41 55 push %r13
ffffffffba333667: 49 89 d5 mov %rdx,%r13
ffffffffba33366a: 41 54 push %r12
ffffffffba33366c: 49 89 f4 mov %rsi,%r12
ffffffffba33366f: 55 push %rbp
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-08-16 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 17:34 Jiri Olsa
2021-08-16 17:49 ` David Hildenbrand
2021-08-16 17:54 ` David Hildenbrand [this message]
2021-08-16 18:12 ` Jiri Olsa
2021-08-16 18:38 ` David Hildenbrand
2021-08-16 19:12 ` Mike Rapoport
2021-08-16 19:20 ` David Hildenbrand
2021-08-17 7:56 ` Mike Rapoport
2021-08-17 8:02 ` David Hildenbrand
2021-08-17 8:20 ` Mike Rapoport
2021-08-17 8:09 ` Jiri Olsa
2021-08-17 7:43 ` Jiri Olsa
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=d05f4d38-fdb8-29a6-202e-19d65cd0b1f1@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jolsa@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--subject='Re: [BUG] general protection fault when reading /proc/kcore' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).