All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: gregkh@linuxfoundation.org, xiangyu.chen@windriver.com
Cc: Christian Brauner <brauner@kernel.org>,
	stable-commits@vger.kernel.org,
	linux-erofs mailing list <linux-erofs@lists.ozlabs.org>
Subject: Re: Patch "erofs: reliably distinguish block based and fscache mode" has been added to the 6.1-stable tree
Date: Fri, 6 Dec 2024 13:05:21 +0800	[thread overview]
Message-ID: <9e9d4558-3e45-4dad-9685-1e3feb693957@linux.alibaba.com> (raw)
In-Reply-To: <2024120228-mocker-refinance-e073@gregkh>

Hi XiangYu,

Just noticed that. Why it's needed for Linux 6.1 LTS?
Just see my reply, I think 6.1 LTS is not impacted:
https://lore.kernel.org/r/686626cd-7dcd-4931-bf55-108522b9bfeb@linux.alibaba.com/

Also, it seems some dependenies are missing, just
backporting this commit will break EROFS.

Hi Greg,

Please help drop this patch from 6.1 queue before more
explanations, thanks!

Thanks,
Gao Xiang

On 2024/12/2 19:48, gregkh@linuxfoundation.org wrote:
> 
> This is a note to let you know that I've just added the patch titled
> 
>      erofs: reliably distinguish block based and fscache mode
> 
> to the 6.1-stable tree which can be found at:
>      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>       erofs-reliably-distinguish-block-based-and-fscache-mode.patch
> and it can be found in the queue-6.1 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 
> 
>  From 7af2ae1b1531feab5d38ec9c8f472dc6cceb4606 Mon Sep 17 00:00:00 2001
> From: Christian Brauner <brauner@kernel.org>
> Date: Fri, 19 Apr 2024 20:36:11 +0800
> Subject: erofs: reliably distinguish block based and fscache mode
> 
> From: Christian Brauner <brauner@kernel.org>
> 
> commit 7af2ae1b1531feab5d38ec9c8f472dc6cceb4606 upstream.
> 
> When erofs_kill_sb() is called in block dev based mode, s_bdev may not
> have been initialised yet, and if CONFIG_EROFS_FS_ONDEMAND is enabled,
> it will be mistaken for fscache mode, and then attempt to free an anon_dev
> that has never been allocated, triggering the following warning:
> 
> ============================================
> ida_free called for id=0 which is not allocated.
> WARNING: CPU: 14 PID: 926 at lib/idr.c:525 ida_free+0x134/0x140
> Modules linked in:
> CPU: 14 PID: 926 Comm: mount Not tainted 6.9.0-rc3-dirty #630
> RIP: 0010:ida_free+0x134/0x140
> Call Trace:
>   <TASK>
>   erofs_kill_sb+0x81/0x90
>   deactivate_locked_super+0x35/0x80
>   get_tree_bdev+0x136/0x1e0
>   vfs_get_tree+0x2c/0xf0
>   do_new_mount+0x190/0x2f0
>   [...]
> ============================================
> 
> Now when erofs_kill_sb() is called, erofs_sb_info must have been
> initialised, so use sbi->fsid to distinguish between the two modes.
> 
> Signed-off-by: Christian Brauner <brauner@kernel.org>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> Reviewed-by: Chao Yu <chao@kernel.org>
> Link: https://lore.kernel.org/r/20240419123611.947084-3-libaokun1@huawei.com
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>   fs/erofs/super.c |    8 ++------
>   1 file changed, 2 insertions(+), 6 deletions(-)
> 
> --- a/fs/erofs/super.c
> +++ b/fs/erofs/super.c
> @@ -892,7 +892,7 @@ static int erofs_init_fs_context(struct
>    */
>   static void erofs_kill_sb(struct super_block *sb)
>   {
> -	struct erofs_sb_info *sbi;
> +	struct erofs_sb_info *sbi = EROFS_SB(sb);
>   
>   	WARN_ON(sb->s_magic != EROFS_SUPER_MAGIC);
>   
> @@ -902,15 +902,11 @@ static void erofs_kill_sb(struct super_b
>   		return;
>   	}
>   
> -	if (erofs_is_fscache_mode(sb))
> +	if (IS_ENABLED(CONFIG_EROFS_FS_ONDEMAND) && sbi->fsid)
>   		kill_anon_super(sb);
>   	else
>   		kill_block_super(sb);
>   
> -	sbi = EROFS_SB(sb);
> -	if (!sbi)
> -		return;
> -
>   	erofs_free_dev_context(sbi->devs);
>   	fs_put_dax(sbi->dax_dev, NULL);
>   	erofs_fscache_unregister_fs(sb);
> 
> 
> Patches currently in stable-queue which might be from brauner@kernel.org are
> 
> queue-6.1/cachefiles-fix-missing-pos-updates-in-cachefiles_ond.patch
> queue-6.1/hfsplus-don-t-query-the-device-logical-block-size-mu.patch
> queue-6.1/netfs-fscache-add-a-memory-barrier-for-fscache_volum.patch
> queue-6.1/fs-inode-prevent-dump_mapping-accessing-invalid-dent.patch
> queue-6.1/initramfs-avoid-filename-buffer-overrun.patch
> queue-6.1/erofs-reliably-distinguish-block-based-and-fscache-mode.patch
> queue-6.1/fs_parser-update-mount_api-doc-to-match-function-sig.patch
> queue-6.1/selftests-mount_setattr-fix-failures-on-64k-page_siz.patch


       reply	other threads:[~2024-12-06  5:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2024120228-mocker-refinance-e073@gregkh>
2024-12-06  5:05 ` Gao Xiang [this message]
2024-12-06  9:33   ` Patch "erofs: reliably distinguish block based and fscache mode" has been added to the 6.1-stable tree Greg KH
2024-12-06  9:41     ` Gao Xiang
2024-12-06 10:03       ` Greg KH
2024-12-06 10:37         ` Gao Xiang
2024-12-06 11:24           ` Greg KH

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=9e9d4558-3e45-4dad-9685-1e3feb693957@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=xiangyu.chen@windriver.com \
    /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.