From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] jfs: reject on-disk inodes of an unsupported type
Date: Sun, 27 Jul 2025 15:36:08 -0400 [thread overview]
Message-ID: <1753631415-e7da4f99@stable.kernel.org> (raw)
In-Reply-To: <20250727100531.533179-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: 8c3f9a70d2d4dd6c640afe294b05c6a0a45434d9
WARNING: Author mismatch between patch and upstream commit:
Backport author: Aditya Dutt <duttaditya18@gmail.com>
Commit author: Dmitry Antipov <dmantipov@yandex.ru>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 8c3f9a70d2d4 ! 1: 2390f42afe00 jfs: reject on-disk inodes of an unsupported type
@@ Metadata
## Commit message ##
jfs: reject on-disk inodes of an unsupported type
+ [ Upstream commit 8c3f9a70d2d4dd6c640afe294b05c6a0a45434d9 ]
+
Syzbot has reported the following BUG:
kernel BUG at fs/inode.c:668!
@@ Commit message
Fixes: 79ac5a46c5c1 ("jfs_lookup(): don't bother with . or ..")
Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
+ Signed-off-by: Aditya Dutt <duttaditya18@gmail.com>
## fs/jfs/jfs_imap.c ##
@@ fs/jfs/jfs_imap.c: static void duplicateIXtree(struct super_block *sb, s64 blkno,
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-5.15.y | Success | Success |
prev parent reply other threads:[~2025-07-27 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 10:05 [PATCH 5.15.y] jfs: reject on-disk inodes of an unsupported type Aditya Dutt
2025-07-27 19:36 ` 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=1753631415-e7da4f99@stable.kernel.org \
--to=sashal@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox