From: Jeongjun Park <aha310510@gmail.com>
To: dave.kleikamp@oracle.com, shaggy@kernel.org
Cc: jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+241c815bda521982cb49@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, willy@infradead.org,
Jeongjun Park <aha310510@gmail.com>
Subject: Re: [PATCH] jfs: Fix array-index-out-of-bounds in diFree
Date: Thu, 30 May 2024 22:28:09 +0900 [thread overview]
Message-ID: <20240530132809.4388-1-aha310510@gmail.com> (raw)
In-Reply-To: <20240426034156.52928-1-aha310510@gmail.com>
>
> Matthew Wilcox wrote:
> > This is not a good commit message.
>
> > > + if(agno >= MAXAG || agno < 0)
> >
> > Please follow normal kernel whitespace rules -- one space between 'if'
> > and the open paren.
>
> Has confirmed. This is a patch that re-edited the relevant part to
> comply with the rules.
>
> Thanks.
>
I have just discovered that the patch I sent last time has been left
unattended. It appears that the vulnerability continues to occur in
version 6.10.0-rc1. I would appreciate it if you could review the patch
and let me know what might be wrong with it.
Regards
Reported-by: syzbot+241c815bda521982cb49@syzkaller.appspotmail.com
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Jeongjun Park <aha310510@gmail.com>
---
fs/jfs/jfs_imap.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/jfs/jfs_imap.c b/fs/jfs/jfs_imap.c
index 2ec35889ad24..1407feccbc2d 100644
--- a/fs/jfs/jfs_imap.c
+++ b/fs/jfs/jfs_imap.c
@@ -290,7 +290,7 @@ int diSync(struct inode *ipimap)
int diRead(struct inode *ip)
{
struct jfs_sb_info *sbi = JFS_SBI(ip->i_sb);
- int iagno, ino, extno, rc;
+ int iagno, ino, extno, rc, agno;
struct inode *ipimap;
struct dinode *dp;
struct iag *iagp;
@@ -339,8 +339,11 @@ int diRead(struct inode *ip)
/* get the ag for the iag */
agstart = le64_to_cpu(iagp->agstart);
+ agno = BLKTOAG(agstart, JFS_SBI(ip->i_sb));
release_metapage(mp);
+ if (agno >= MAXAG || agno < 0)
+ return -EIO;
rel_inode = (ino & (INOSPERPAGE - 1));
pageno = blkno >> sbi->l2nbperpage;
--
2.34.1
next prev parent reply other threads:[~2024-05-30 13:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:25 [syzbot] [jfs?] UBSAN: array-index-out-of-bounds in diFree syzbot
2024-04-24 4:11 ` Jeongjun Park
2024-04-24 4:39 ` syzbot
2024-04-24 17:22 ` [PATCH] jfs: Fix " Jeongjun Park
2024-04-24 17:41 ` Matthew Wilcox
2024-04-25 12:44 ` Jeongjun Park
2024-04-25 12:53 ` Matthew Wilcox
2024-04-25 14:10 ` Jeongjun Park
2024-04-25 14:14 ` Dave Kleikamp
2024-04-25 14:17 ` Matthew Wilcox
2024-04-25 14:24 ` Jeongjun Park
2024-04-25 17:04 ` Matthew Wilcox
2024-04-26 1:42 ` Jeongjun Park
2024-04-26 2:34 ` Jeongjun Park
2024-04-26 3:27 ` Matthew Wilcox
2024-04-26 3:41 ` Jeongjun Park
2024-05-30 13:28 ` Jeongjun Park [this message]
2024-06-26 17:40 ` Dave Kleikamp
2024-04-25 14:24 ` Dave Kleikamp
2024-04-25 14:37 ` Jeongjun Park
2024-04-25 3:15 ` [syzbot] [jfs?] UBSAN: " Jeongjun Park
2024-04-25 4:33 ` syzbot
2024-04-25 4:59 ` Jeongjun Park
2024-04-25 5:50 ` syzbot
2024-04-25 8:56 ` Jeongjun Park
2024-04-25 9:23 ` syzbot
2024-04-25 9:04 ` Jeongjun Park
2024-04-25 9:39 ` syzbot
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=20240530132809.4388-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+241c815bda521982cb49@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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.