From: Matthew Wilcox <willy@infradead.org>
To: Jeongjun Park <aha310510@gmail.com>
Cc: dave.kleikamp@oracle.com, brauner@kernel.org,
jfs-discussion@lists.sourceforge.net, jlayton@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
shaggy@kernel.org,
syzbot+241c815bda521982cb49@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] jfs: Fix array-index-out-of-bounds in diFree
Date: Fri, 26 Apr 2024 04:27:40 +0100 [thread overview]
Message-ID: <ZisfLI3Va6D5PjT6@casper.infradead.org> (raw)
In-Reply-To: <20240426023412.52281-1-aha310510@gmail.com>
On Fri, Apr 26, 2024 at 11:34:12AM +0900, Jeongjun Park wrote:
> I forgot to add Dave to the cc, so I'm sending it again.
>
> Send final patch. With the patch that modified the location of
> release_metapage(), out-of-bounds vulnerabilities can now be
> sufficiently prevented.
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.
next prev parent reply other threads:[~2024-04-26 3:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:25 [syzbot] [jfs?] UBSAN: " 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 [this message]
2024-04-26 3:41 ` Jeongjun Park
2024-05-30 13:28 ` Jeongjun Park
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=ZisfLI3Va6D5PjT6@casper.infradead.org \
--to=willy@infradead.org \
--cc=aha310510@gmail.com \
--cc=brauner@kernel.org \
--cc=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlayton@kernel.org \
--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 \
/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
all inboxes | Powered by JetHome®