From: Andrew Kanner <andrew.kanner@gmail.com>
To: shaggy@kernel.org, jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
Andrew Kanner <andrew.kanner@gmail.com>
Subject: [PATCH 0/1] fs/jfs: fix KASAN double-free warnings after failed jfs_remount()
Date: Sat, 1 Jul 2023 17:05:41 +0300 [thread overview]
Message-ID: <20230701140542.2252-1-andrew.kanner@gmail.com> (raw)
In-Reply-To: <20221201124628.603505-1-liushixin2@huawei.com>
+Tested-by: Andrew Kanner <andrew.kanner@gmail.com>
for https://lore.kernel.org/all/20221201124628.603505-1-liushixin2@huawei.com/T/
The next change complements the patch from Liu Shixin (see above).
Two patches for fs/jfs/jfs_{imap,dmap}.c fix syzkaller issues:
Link: https://syzkaller.appspot.com/bug?extid=9f06ddd18bf059dff2ad
Link: https://syzkaller.appspot.com/bug?extid=6a93efb725385bc4b2e9
Link: https://syzkaller.appspot.com/bug?extid=90a11e6b1e810785c6ff
Link: https://syzkaller.appspot.com/bug?extid=47366a6b503c7edf6bbb
And Similar bugs from the other branches:
Link: https://syzkaller.appspot.com/bug?extid=cfff8c52c283dd09bf27
Link: https://syzkaller.appspot.com/bug?extid=e8f9034a130a66a2b351
Link: https://syzkaller.appspot.com/bug?extid=5c604c1cc148275ab8a6
Link: https://syzkaller.appspot.com/bug?extid=ea731a6641531af62f80
Link: https://syzkaller.appspot.com/bug?extid=b212249c28280daa4576
Andrew Kanner (1):
fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount()
fs/jfs/jfs_dmap.c | 1 +
1 file changed, 1 insertion(+)
--
2.39.3
next prev parent reply other threads:[~2023-07-01 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:46 [PATCH] jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount Liu Shixin
2023-07-01 14:05 ` Andrew Kanner [this message]
2023-07-01 14:05 ` [PATCH 1/1] fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() Andrew Kanner
2023-07-18 15:39 ` Andrew Kanner
2023-07-18 16:17 ` Dave Kleikamp
2023-07-18 19:46 ` Dave Kleikamp
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=20230701140542.2252-1-andrew.kanner@gmail.com \
--to=andrew.kanner@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@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
all inboxes | Powered by JetHome®