From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: jack@suse.cz, akpm@linux-foundation.org, arnd@arndb.de,
linux.bhar@gmail.com, hariprasad.kelam@gmail.com
Cc: reiserfs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: [PATCH] fs: reiserfs: Fix possible null-pointer dereferences in remove_from_transaction()
Date: Fri, 26 Jul 2019 16:38:38 +0800 [thread overview]
Message-ID: <20190726083838.8301-1-baijiaju1990@gmail.com> (raw)
In remove_from_transaction(), there is an if statement on line 3447 to
check whether bh is NULL:
if (bh)
When bh is NULL, it is used on line 3450:
clear_buffer_journaled(bh);
and lines 3453-3456:
clear_buffer_journal_dirty(bh);
clear_buffer_dirty(bh);
clear_buffer_journal_test(bh);
put_bh(bh);
Thus, possible null-pointer dereferences may occur.
To fix these bugs, bh is checked before being used.
These bugs are found by a static analysis tool STCheck written by us.
Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
---
fs/reiserfs/journal.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/reiserfs/journal.c b/fs/reiserfs/journal.c
index 4517a1394c6f..d115578597b6 100644
--- a/fs/reiserfs/journal.c
+++ b/fs/reiserfs/journal.c
@@ -3444,12 +3444,13 @@ static int remove_from_transaction(struct super_block *sb,
if (cn == journal->j_last) {
journal->j_last = cn->prev;
}
- if (bh)
+ if (bh) {
remove_journal_hash(sb, journal->j_hash_table, NULL,
bh->b_blocknr, 0);
- clear_buffer_journaled(bh); /* don't log this one */
+ clear_buffer_journaled(bh); /* don't log this one */
+ }
- if (!already_cleaned) {
+ if (!already_cleaned && bh) {
clear_buffer_journal_dirty(bh);
clear_buffer_dirty(bh);
clear_buffer_journal_test(bh);
--
2.17.0
next reply other threads:[~2019-07-26 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 8:38 Jia-Ju Bai [this message]
2019-07-26 22:54 ` Andrew Morton
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=20190726083838.8301-1-baijiaju1990@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=hariprasad.kelam@gmail.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@gmail.com \
--cc=reiserfs-devel@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
all inboxes | Powered by JetHome®