From: Frank Scheiner <frank.scheiner@web.de>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Christoph Hellwig <hch@lst.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Sparc kernel list <sparclinux@vger.kernel.org>,
debian-sparc <debian-sparc@lists.debian.org>
Subject: Re: Regression in 028abd92 for Sun UltraSPARC T1
Date: Wed, 24 Mar 2021 16:58:39 +0100 [thread overview]
Message-ID: <250aaeb3-40fe-60c7-044e-aa9daacd7c12@web.de> (raw)
In-Reply-To: <p1p52s61-n8p-s29n-n195-q22rs07qoq40@vanv.qr>
On 24.03.21 16:22, Jan Engelhardt wrote:
>
> On Wednesday 2021-03-24 14:57, Frank Scheiner wrote:
>
>> (gdb) l *(sys_mount+0x114/0x1e0)
>> 0x6c6380 is in __se_sys_mount (fs/namespace.c:3390).
>
> /0x1e0 does not normally belong there. Just
>
> l *(sys_mount+0x114)
>
I guess this comes from my log on [1]:
```
[...]
[ 20.089289] RPC: <kfree+0x3ac/0x420>
[ 20.089415] l0: ffff8001f8885cc8 l1: ffff8001f8881380 l2:
ffff8001ec434558 l3: 0000000000201db0
[ 20.089586] l4: 000000000000029c l5: ffff80010000c1a0 l6:
ffff8001ec79c000 l7: 00000000006c6380
[ 20.089802] i0: 0000000000001000 i1: ffff8001ec436000 i2:
00000000006c6494 i3: ffff8001ec436000
[ 20.089877] i4: ffff800008405340 i5: 00006000045396c0 i6:
ffff8001ec79f561 i7: 00000000006c6494
[ 20.090051] I7: <sys_mount+0x114/0x1e0>
[ 20.090186] Call Trace:
[ 20.090279] [<00000000006c6494>] sys_mount+0x114/0x1e0
[ 20.090338] [<00000000006c6454>] sys_mount+0xd4/0x1e0
[ 20.090499] [<0000000000406274>] linux_sparc_syscall+0x34/0x44
[ 20.090697] Disabling lock debugging due to kernel taint
[ 20.090770] Caller[00000000006c6494]: sys_mount+0x114/0x1e0
[ 20.090926] Caller[00000000006c6454]: sys_mount+0xd4/0x1e0
[ 20.091133] Caller[0000000000406274]: linux_sparc_syscall+0x34/0x44
[ 20.091196] Caller[0000000000100aa8]: 0x100aa8
[...]
```
[1]: https://pastebin.com/ApPYsMcu
Here the result for the suggested command:
```
root@t1000:~/mnt/torvalds-linux# gdb -q vmlinux
Reading symbols from vmlinux...
(gdb) l *(sys_mount+0x114)
0x6c6494 is in __se_sys_mount (fs/namespace.c:3415).
3410 if (IS_ERR(options))
3411 goto out_data;
3412
3413 ret = do_mount(kernel_dev, dir_name, kernel_type, flags, options);
3414
3415 kfree(options);
3416 out_data:
3417 kfree(kernel_dev);
3418 out_dev:
3419 kfree(kernel_type);
(gdb)
```
Cheers,
Frank
next prev parent reply other threads:[~2021-03-24 15:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 21:30 Regression in 028abd92 for Sun UltraSPARC T1 Frank Scheiner
2021-03-22 21:48 ` John Paul Adrian Glaubitz
2021-03-22 21:55 ` Frank Scheiner
2021-03-23 16:50 ` Jan Engelhardt
2021-03-23 16:57 ` Christoph Hellwig
2021-03-23 17:39 ` Frank Scheiner
2021-03-23 22:17 ` Frank Scheiner
2021-03-24 8:28 ` Christoph Hellwig
2021-03-24 12:30 ` Frank Scheiner
2021-03-24 12:42 ` Anatoly Pugachev
2021-03-24 12:48 ` Frank Scheiner
2021-03-24 12:49 ` John Paul Adrian Glaubitz
2021-03-24 13:09 ` Frank Scheiner
2021-03-24 13:16 ` John Paul Adrian Glaubitz
2021-03-24 13:19 ` Frank Scheiner
2021-03-24 13:24 ` Anatoly Pugachev
2021-03-24 13:29 ` Frank Scheiner
2021-03-24 13:57 ` Frank Scheiner
2021-03-24 15:22 ` Jan Engelhardt
2021-03-24 15:58 ` Frank Scheiner [this message]
2021-03-24 16:10 ` Christoph Hellwig
2021-03-24 16:33 ` Frank Scheiner
2021-03-24 16:37 ` Frank Scheiner
2021-03-25 7:50 ` Christoph Hellwig
2025-09-02 20:18 ` John Paul Adrian Glaubitz
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=250aaeb3-40fe-60c7-044e-aa9daacd7c12@web.de \
--to=frank.scheiner@web.de \
--cc=debian-sparc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=jengelh@inai.de \
--cc=sparclinux@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 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).