All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 1/2] exfat: support dynamic allocate bh for exfat_entry_set_cache
Date: Sun, 15 Dec 2024 12:51:35 -0500	[thread overview]
Message-ID: <20241215091934-2cc7facb6ab36cb2@stable.kernel.org> (raw)
In-Reply-To: <20241214221839.3274375-1-harshit.m.mogalapalli@oracle.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: a3ff29a95fde16906304455aa8c0bd84eb770258

WARNING: Author mismatch between patch and upstream commit:
Backport author: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Commit author: Yuezhang Mo <Yuezhang.Mo@sony.com>


Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Not found

Note: The patch differs from the upstream commit:
---
1:  a3ff29a95fde ! 1:  bb39fa77df0f exfat: support dynamic allocate bh for exfat_entry_set_cache
    @@ Metadata
      ## Commit message ##
         exfat: support dynamic allocate bh for exfat_entry_set_cache
     
    +    [ Upstream commit a3ff29a95fde16906304455aa8c0bd84eb770258 ]
    +
         In special cases, a file or a directory may occupied more than 19
         directory entries, pre-allocating 3 bh is not enough. Such as
           - Support vendor secondary directory entry in the future.
    @@ Commit message
         Reviewed-by: Aoyama Wataru <wataru.aoyama@sony.com>
         Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>
         Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
    +    (cherry picked from commit a3ff29a95fde16906304455aa8c0bd84eb770258)
    +    [Harshit: Backport - clean cherry-pick to 6.1.y]
    +    Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
     
      ## fs/exfat/dir.c ##
     @@ fs/exfat/dir.c: int exfat_free_dentry_set(struct exfat_entry_set_cache *es, int sync)
    @@ fs/exfat/dir.c: struct exfat_entry_set_cache *exfat_get_dentry_set(struct super_
     
      ## fs/exfat/exfat_fs.h ##
     @@ fs/exfat/exfat_fs.h: struct exfat_entry_set_cache {
    - 	struct super_block *sb;
    + 	bool modified;
      	unsigned int start_off;
      	int num_bh;
     -	struct buffer_head *bh[DIR_CACHE_SIZE];
     +	struct buffer_head *__bh[DIR_CACHE_SIZE];
     +	struct buffer_head **bh;
      	unsigned int num_entries;
    - 	bool modified;
      };
      
     +#define IS_DYNAMIC_ES(es)	((es)->__bh != (es)->bh)
---

Results of testing on various branches:

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

      parent reply	other threads:[~2024-12-15 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 22:18 [PATCH 6.1.y 1/2] exfat: support dynamic allocate bh for exfat_entry_set_cache Harshit Mogalapalli
2024-12-14 22:18 ` [PATCH 6.1.y 2/2] exfat: fix potential deadlock on __exfat_get_dentry_set Harshit Mogalapalli
2024-12-15 17:51   ` Sasha Levin
2024-12-15 17:51 ` 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=20241215091934-2cc7facb6ab36cb2@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=harshit.m.mogalapalli@oracle.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.