From: Frank Scheiner <frank.scheiner@web.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Engelhardt <jengelh@inai.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 17:37:10 +0100 [thread overview]
Message-ID: <b8e98852-8e90-2860-a051-2173da2805c7@web.de> (raw)
In-Reply-To: <092f6c45-d4fe-ac02-d416-e644e2f26795@web.de>
On 24.03.21 17:33, Frank Scheiner wrote:
> On 24.03.21 17:10, Christoph Hellwig wrote:
>> On Wed, Mar 24, 2021 at 04:58:39PM +0100, Frank Scheiner wrote:
>>> [ 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:
>>
>> Thanks. And very strange, as i can't find what would free options
>> before. Does the system boot if you comment out that kfree in line
>> 3415 (even if that casues a memleak elsewhere).
>
> Unfortunately not, the result with the kfree() commented in
> fs/namespace.c:3415 looks pretty similar in my eyes.
Actually on second view the result looks different. :-/
next prev parent reply other threads:[~2021-03-24 16:38 UTC|newest]
Thread overview: 24+ 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
2021-03-24 16:10 ` Christoph Hellwig
2021-03-24 16:33 ` Frank Scheiner
2021-03-24 16:37 ` Frank Scheiner [this message]
2021-03-25 7:50 ` Christoph Hellwig
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=b8e98852-8e90-2860-a051-2173da2805c7@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).