From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Aditya Dutt <duttaditya18@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] jfs: define xtree root and page independently
Date: Tue, 29 Apr 2025 08:50:28 -0400 [thread overview]
Message-ID: <20250429010144-cc4c7c112c3ef809@stable.kernel.org> (raw)
In-Reply-To: <20250427154539.96678-1-duttaditya18@gmail.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: a779ed754e52d582b8c0e17959df063108bd0656
WARNING: Author mismatch between patch and upstream commit:
Backport author: Aditya Dutt<duttaditya18@gmail.com>
Commit author: Dave Kleikamp<dave.kleikamp@oracle.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 2ff51719ec61)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: a779ed754e52d ! 1: cac2f05e71c44 jfs: define xtree root and page independently
@@ Metadata
## Commit message ##
jfs: define xtree root and page independently
+ [ Upstream commit a779ed754e52d582b8c0e17959df063108bd0656 ]
+
In order to make array bounds checking sane, provide a separate
definition of the in-inode xtree root and the external xtree page.
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Tested-by: Manas Ghandat <ghandatmanas@gmail.com>
+ (cherry picked from commit a779ed754e52d582b8c0e17959df063108bd0656)
+ Closes: https://syzkaller.appspot.com/bug?extid=ccb458b6679845ee0bae
+ Reported-by: syzbot+ccb458b6679845ee0bae@syzkaller.appspotmail.com
+ Signed-off-by: Aditya Dutt <duttaditya18@gmail.com>
## fs/jfs/jfs_dinode.h ##
@@ fs/jfs/jfs_dinode.h: struct dinode {
@@ fs/jfs/jfs_xtree.c: xtSplitRoot(tid_t tid,
INCREMENT(xtStat.split);
-@@ fs/jfs/jfs_xtree.c: int xtAppend(tid_t tid, /* transaction id */
+@@ fs/jfs/jfs_xtree.c: static int xtRelink(tid_t tid, struct inode *ip, xtpage_t * p)
*/
void xtInitRoot(tid_t tid, struct inode *ip)
{
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-04-29 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 15:45 [PATCH 5.15.y] jfs: define xtree root and page independently Aditya Dutt
2025-04-29 12:50 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-15 18:09 Aditya Dutt
2025-04-15 20:18 ` Aditya Dutt
2025-04-15 23:07 ` Sasha Levin
2025-04-22 13:28 ` Greg KH
2025-04-15 18:08 Aditya Dutt
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=20250429010144-cc4c7c112c3ef809@stable.kernel.org \
--to=sashal@kernel.org \
--cc=duttaditya18@gmail.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.