From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: caiqingfu <baicaiaichibaicai@gmail.com>
Cc: senozhatsky@chromium.org, akpm@linux-foundation.org,
caiqingfu@ruijie.com.cn, minchan@kernel.org,
mm-commits@vger.kernel.org
Subject: Re: [PATCH] zram: panic when use ext4 over zram
Date: Mon, 2 Dec 2024 16:04:43 +0900 [thread overview]
Message-ID: <20241202070443.GA886051@google.com> (raw)
In-Reply-To: <20241202060632.139067-1-baicaiaichibaicai@gmail.com>
On (24/12/02 14:06), caiqingfu wrote:
> [ 46.560092] page_owner tracks the page as allocated
> [ 46.560101] page last allocated via order 0, migratetype Movable, gfp_mask 0x148c48(GFP_NOFS|__GFP_NOFAIL|__GFP_COMP|__GFP_HARDWALL|__GFP_MOVABLE), pid 1769, tgid 1372 (a.out), ts 45588110160, free_ts 45123127760
> [ 46.560126] prep_new_page+0xa8/0x10c
> [ 46.560143] get_page_from_freelist+0xa44/0x16d0
> [ 46.560160] __alloc_pages_noprof+0x150/0x290
> [ 46.560177] alloc_pages_mpol_noprof+0x88/0x23c
> [ 46.560195] alloc_pages_noprof+0x4c/0x7c
> [ 46.560234] folio_alloc_noprof+0x14/0x64
> [ 46.560254] filemap_alloc_folio_noprof+0x100/0x14c
> [ 46.560272] __filemap_get_folio+0x21c/0x38c
> [ 46.560290] bdev_getblk+0xd0/0x2b4
> [ 46.560304] __ext4_get_inode_loc+0x11c/0x53c
> [ 46.560320] ext4_get_inode_loc+0x44/0xb0
> [ 46.560337] ext4_reserve_inode_write+0x40/0xf0
> [ 46.560354] __ext4_mark_inode_dirty+0x4c/0x1f0
> [ 46.560370] ext4_ext_tree_init+0x40/0x4c
> [ 46.560388] __ext4_new_inode+0x790/0x13b8
> [ 46.560406] ext4_create+0xdc/0x1d0
>
> and other list this:
>
> [ 47.683962] page_owner tracks the page as allocated
> [ 47.684012] page last allocated via order 0, migratetype Unmovable, gfp_mask 0x148c40(GFP_NOFS|__GFP_NOFAIL|__GFP_COMP|__GFP_HARDWALL), pid 1309, tgid 970 (a.out), ts 44091572544, free_ts 0
> [ 47.684056] prep_new_page+0xa8/0x10c
> [ 47.684090] get_page_from_freelist+0xa44/0x16d0
> [ 47.684109] __alloc_pages_noprof+0x150/0x290
> [ 47.684127] alloc_pages_mpol_noprof+0x88/0x23c
> [ 47.684148] alloc_pages_noprof+0x4c/0x7c
> [ 47.684166] folio_alloc_noprof+0x14/0x64
> [ 47.684184] filemap_alloc_folio_noprof+0x100/0x14c
> [ 47.684205] __filemap_get_folio+0x21c/0x38c
> [ 47.684223] bdev_getblk+0xd0/0x2b4
> [ 47.684240] ext4_getblk+0xac/0x300
> [ 47.684258] ext4_bread+0x14/0xe4
> [ 47.684274] ext4_append+0x90/0x1cc
> [ 47.684293] do_split+0x88/0x9c4
> [ 47.684307] make_indexed_dir+0x580/0x688
> [ 47.684322] ext4_add_entry+0x37c/0x420
> [ 47.684337] ext4_add_nondir+0x38/0x11c
>
> It look like only the file system metadata has been modified.I'm not sure.
What's your use-case, what apps you run and what data is stored
on zram disk?
next prev parent reply other threads:[~2024-12-02 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 11:57 [PATCH] zram: panic when use ext4 over zram caiqingfu
2024-11-30 5:32 ` Sergey Senozhatsky
2024-12-02 6:06 ` caiqingfu
2024-12-02 7:04 ` Sergey Senozhatsky [this message]
2024-12-02 10:07 ` caiqingfu
2024-12-10 9:34 ` Sergey Senozhatsky
2024-12-11 11:04 ` Sergey Senozhatsky
2024-12-12 9:55 ` caiqingfu
2024-12-13 4:28 ` Sergey Senozhatsky
2024-12-13 5:56 ` caiqingfu
2024-12-13 6:28 ` Sergey Senozhatsky
2024-12-13 6:40 ` Sergey Senozhatsky
2024-12-15 8:57 ` caiqingfu
2024-12-15 9:12 ` Sergey Senozhatsky
2024-12-16 1:24 ` caiqingfu
2024-12-12 18:40 ` Kees Bakker
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=20241202070443.GA886051@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=baicaiaichibaicai@gmail.com \
--cc=caiqingfu@ruijie.com.cn \
--cc=minchan@kernel.org \
--cc=mm-commits@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.