All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 211329] New: XFS related memory leak on ppc64le
Date: Sun, 24 Jan 2021 23:02:25 +0000	[thread overview]
Message-ID: <bug-211329-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=211329

            Bug ID: 211329
           Summary: XFS related memory leak on ppc64le
           Product: File System
           Version: 2.5
    Kernel Version: =>5.10.10
          Hardware: PPC-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: cam@neo-zeon.de
        Regression: No

Not necessarily ppc64le specific, but so far I'm only seeing this on my Talos
II system with XFS and none of my amd64 systems. 5.10.10 is the only 5.10.x
series kernel tested so far. Issue may have started earlier.

These are the only leaks so far with the box up for several hours. Not sure how
serious this is.

Specs:
2x 18 Core POWER9
512 GB memory

The XFS filesystems on this system:
df -h / /home
Filesystem      Size  Used Avail Use% Mounted on
/dev/md1        1.8T   59G  1.8T   4% /
/dev/bcache0     14T  634G   14T   5% /home

cat /sys/kernel/debug/kmemleak
unreferenced object 0xc0000011c63af400 (size 512):
  comm "worker", pid 7351, jiffies 4295245272 (age 21394.586s)
  hex dump (first 32 bytes):
    c0 e0 58 3c 00 00 00 c0 08 f4 3a c6 11 00 00 c0  ..X<......:.....
    08 f4 3a c6 11 00 00 c0 18 2a 3a c6 11 00 00 c0  ..:......*:.....
  backtrace:
    [<000000005f1fe84c>] blkg_alloc+0x58/0x260
    [<00000000bb469d61>] blkg_create+0x3b0/0x570
    [<000000007d35bf0d>] bio_associate_blkg_from_css+0x318/0x480
    [<00000000a4cfa6ed>] bio_associate_blkg+0x44/0xb0
    [<0000000014c40666>] cached_dev_submit_bio+0x140/0x1090
    [<000000001e375f40>] submit_bio_noacct+0x12c/0x5e0
    [<000000005d621ecf>] submit_bio+0x5c/0x270
    [<000000000d4d6bf5>] iomap_readahead+0xdc/0x230
    [<00000000b0093137>] xfs_vm_readahead+0x28/0x40
    [<00000000c7837a39>] read_pages+0xcc/0x370
    [<00000000ace2d2cc>] page_cache_ra_unbounded+0x1a4/0x280
    [<00000000ea5f8116>] generic_file_buffered_read+0x4cc/0xbd0
    [<00000000ce5a2b3b>] xfs_file_buffered_aio_read+0x70/0x130
    [<0000000019bddea7>] xfs_file_read_iter+0xa0/0x150
    [<0000000082a5c085>] new_sync_read+0x14c/0x1d0
    [<00000000abee86d0>] vfs_read+0x1a0/0x210
unreferenced object 0xc00000001772a840 (size 64):
  comm "worker", pid 7351, jiffies 4295245272 (age 21394.586s)
  hex dump (first 32 bytes):
    dc 5f 00 00 00 00 00 00 50 97 80 00 00 00 00 c0  ._......P.......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<000000006e666d7e>] percpu_ref_init+0x7c/0x150
    [<00000000ac923962>] blkg_alloc+0x84/0x260
    [<00000000bb469d61>] blkg_create+0x3b0/0x570
    [<000000007d35bf0d>] bio_associate_blkg_from_css+0x318/0x480
    [<00000000a4cfa6ed>] bio_associate_blkg+0x44/0xb0
    [<0000000014c40666>] cached_dev_submit_bio+0x140/0x1090
    [<000000001e375f40>] submit_bio_noacct+0x12c/0x5e0
    [<000000005d621ecf>] submit_bio+0x5c/0x270
    [<000000000d4d6bf5>] iomap_readahead+0xdc/0x230
    [<00000000b0093137>] xfs_vm_readahead+0x28/0x40
    [<00000000c7837a39>] read_pages+0xcc/0x370
    [<00000000ace2d2cc>] page_cache_ra_unbounded+0x1a4/0x280
    [<00000000ea5f8116>] generic_file_buffered_read+0x4cc/0xbd0
    [<00000000ce5a2b3b>] xfs_file_buffered_aio_read+0x70/0x130
    [<0000000019bddea7>] xfs_file_read_iter+0xa0/0x150
    [<0000000082a5c085>] new_sync_read+0x14c/0x1d0

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-01-24 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24 23:02 bugzilla-daemon [this message]
2021-01-24 23:16 ` [Bug 211329] XFS related memory leak on ppc64le bugzilla-daemon
2021-01-25  0:20 ` bugzilla-daemon
2021-01-25  0:38 ` bugzilla-daemon
2021-01-25  1:56 ` bugzilla-daemon
2021-01-25  2:15 ` bugzilla-daemon
2021-01-26 17:02 ` [Bug 211329] blkg_alloc " bugzilla-daemon
2021-01-30 16:32 ` bugzilla-daemon
2021-01-31  6:44 ` bugzilla-daemon

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=bug-211329-201763@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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 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.