All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: lanbincn@qq.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] f2fs: fix null-ptr-deref in f2fs_submit_page_bio()
Date: Fri, 10 Jan 2025 12:39:14 -0500	[thread overview]
Message-ID: <20250110103606-aaa23db4e384ba9c@stable.kernel.org> (raw)
In-Reply-To: <tencent_870C520322ED6ECDC9078DE499753B0E1506@qq.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa

WARNING: Author mismatch between patch and upstream commit:
Backport author: lanbincn@qq.com
Commit author: Ye Bin<yebin10@huawei.com>


Status in newer kernel trees:
6.12.y | Present (different SHA1: 9e11b1d5fda9)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  b7d0a97b2808 ! 1:  73a09904eb0d f2fs: fix null-ptr-deref in f2fs_submit_page_bio()
    @@ Metadata
      ## Commit message ##
         f2fs: fix null-ptr-deref in f2fs_submit_page_bio()
     
    +    [ Upstream commit b7d0a97b28083084ebdd8e5c6bccd12e6ec18faa ]
    +
         There's issue as follows when concurrently installing the f2fs.ko
         module and mounting the f2fs file system:
         KASAN: null-ptr-deref in range [0x0000000000000020-0x0000000000000027]
    @@ Commit message
         Signed-off-by: Ye Bin <yebin10@huawei.com>
         Reviewed-by: Chao Yu <chao@kernel.org>
         Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
    +    Signed-off-by: Bin Lan <lanbincn@qq.com>
     
      ## fs/f2fs/super.c ##
     @@ fs/f2fs/super.c: static int __init init_f2fs_fs(void)
    - 	err = f2fs_init_shrinker();
    + 	err = register_shrinker(&f2fs_shrinker_info, "f2fs-shrinker");
      	if (err)
      		goto free_sysfs;
     -	err = register_filesystem(&f2fs_fs_type);
    @@ fs/f2fs/super.c: static int __init init_f2fs_fs(void)
      	f2fs_destroy_root_stats();
     -	unregister_filesystem(&f2fs_fs_type);
     -free_shrinker:
    - 	f2fs_exit_shrinker();
    + 	unregister_shrinker(&f2fs_shrinker_info);
      free_sysfs:
      	f2fs_exit_sysfs();
     @@ fs/f2fs/super.c: static int __init init_f2fs_fs(void)
    @@ fs/f2fs/super.c: static void __exit exit_f2fs_fs(void)
      	f2fs_destroy_post_read_processing();
      	f2fs_destroy_root_stats();
     -	unregister_filesystem(&f2fs_fs_type);
    - 	f2fs_exit_shrinker();
    + 	unregister_shrinker(&f2fs_shrinker_info);
      	f2fs_exit_sysfs();
      	f2fs_destroy_garbage_collection_cache();
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |

      reply	other threads:[~2025-01-10 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 12:08 [PATCH 6.6.y] f2fs: fix null-ptr-deref in f2fs_submit_page_bio() lanbincn
2025-01-10 17:39 ` Sasha Levin [this message]

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=20250110103606-aaa23db4e384ba9c@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=lanbincn@qq.com \
    --cc=stable@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.