sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 14:09:02 +0100	[thread overview]
Message-ID: <8600c0fc-7144-4b38-d6ae-4dbbabb125ba@web.de> (raw)
In-Reply-To: <20210324082817.GA2625@lst.de>



On 24.03.21 09:28, Christoph Hellwig wrote:
> On Tue, Mar 23, 2021 at 11:17:41PM +0100, Frank Scheiner wrote:
>> 028abd9222df0cf5855dab5014a5ebaf06f90565
>>
>> ...is broken on my T1000.
>>
>> As I don't know how big attachments can be on this list, I put the logs
>> on pastebin.
>>
>> A log for 028abd9222df is here:
>>
>> https://pastebin.com/ApPYsMcu
>
> Just do confirm:  in this tree line 304 in mm/slub.c is this BUG_ON:
>
> 	BUG_ON(object == fp); /* naive detection of double free or corruption */
>
> which would mean we have a double free.  In that case it would be
> interesting which call to kfree this is, which could be done by
> calling gdb on vmlinux and then typing;
>
> l *(sys_mount+0x114/0x1e0)
>
> Not that a double free caused by this conversion makes any sense to me..

This is what I get:

```
root@t1000:~/kernels-in-question# gdb vmlinux-028abd9222df-new
GNU gdb (Debian 9.2-1+b1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "sparc64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
     <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vmlinux-028abd9222df-new...
(gdb) l *(sys_mount+0x114/0x1e0)
0x6c6380 is in __se_sys_mount (fs/namespace.c:3390).
3385	fs/namespace.c: No such file or directory.
(gdb)
```

Kernel sources are not available on the T1000.

If need be, where do they need to exist and how should the directory be
named - `/usr/src/[...]`?

Cheers,
Frank

  parent reply	other threads:[~2021-03-24 13:10 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 [this message]
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
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=8600c0fc-7144-4b38-d6ae-4dbbabb125ba@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).