mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Julian Sun <sunjunchao2870@gmail.com>, ocfs2-devel@lists.linux.dev
Cc: lbec@evilplan.org, mark@fasheh.com,
	syzbot+05b9b39d8bdfe1a0861f@syzkaller.appspotmail.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH v2] ocfs2: fix null-ptr-deref when journal load failed.
Date: Fri, 30 Aug 2024 18:58:48 +0800	[thread overview]
Message-ID: <fe86da76-555d-424a-828f-ea99b05b363f@linux.alibaba.com> (raw)
In-Reply-To: <cf4174af158587cabd525ae23d35c0b399eade47.camel@gmail.com>



On 8/30/24 6:11 PM, Julian Sun wrote:
> On Fri, 2024-08-30 at 17:40 +0800, Joseph Qi wrote:
>>
>>
>> On 8/23/24 4:31 PM, Julian Sun wrote:
>>> During the mounting process, if journal_reset() fails
>>> because of too short journal, then lead to
>>> jbd2_journal_load() fails with NULL j_sb_buffer.
>>> Subsequently, ocfs2_journal_shutdown() calls
>>> jbd2_journal_flush()->jbd2_cleanup_journal_tail()->
>>> __jbd2_update_log_tail()->jbd2_journal_update_sb_log_tail()
>>> ->lock_buffer(journal->j_sb_buffer), resulting in a
>>> null-pointer dereference error.
>>>
>>> To resolve this issue, a new state OCFS2_JOURNAL_INITED
>>> has been introduced to replace the previous functionality
>>> of OCFS2_JOURNAL_LOADED, the original OCFS2_JOURNAL_LOADED
>>> is only set when ocfs2_journal_load() is successful.
>>> The jbd2_journal_flush() function is allowed to be called
>>> only when this flag is set. The logic here is that if the
>>> journal has even not been successfully loaded, there is
>>> no need to flush the journal.
>>>
>>> Link: https://syzkaller.appspot.com/bug?extid=05b9b39d8bdfe1a0861f
>>> Reported-by: syzbot+05b9b39d8bdfe1a0861f@syzkaller.appspotmail.com
>>> Signed-off-by: Julian Sun <sunjunchao2870@gmail.com>
>>> ---
>>>  fs/ocfs2/journal.c | 9 ++++++---
>>>  fs/ocfs2/journal.h | 1 +
>>>  2 files changed, 7 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/fs/ocfs2/journal.c b/fs/ocfs2/journal.c
>>> index 530fba34f6d3..da0ffcc5de0a 100644
>>> --- a/fs/ocfs2/journal.c
>>> +++ b/fs/ocfs2/journal.c
>>> @@ -968,7 +968,7 @@ int ocfs2_journal_init(struct ocfs2_super *osb,
>>> int *dirty)
>>>  
>>>         ocfs2_set_journal_params(osb);
>>>  
>>> -       journal->j_state = OCFS2_JOURNAL_LOADED;
>>> +       journal->j_state = OCFS2_JOURNAL_INITED;
>>>  
>>>         status = 0;
>>>  done:
>>> @@ -1039,6 +1039,7 @@ void ocfs2_journal_shutdown(struct
>>> ocfs2_super *osb)
>>>         int status = 0;
>>>         struct inode *inode = NULL;
>>>         int num_running_trans = 0;
>>> +       enum ocfs2_journal_state state;
>>>  
>>>         BUG_ON(!osb);
>>>  
>>> @@ -1047,8 +1048,9 @@ void ocfs2_journal_shutdown(struct
>>> ocfs2_super *osb)
>>>                 goto done;
>>>  
>>>         inode = journal->j_inode;
>>> +       state = journal->j_state;
>>>  
>>> -       if (journal->j_state != OCFS2_JOURNAL_LOADED)
>>> +       if (state != OCFS2_JOURNAL_INITED && state !=
>>> OCFS2_JOURNAL_LOADED)
>>>                 goto done;
>>>  
>>>         /* need to inc inode use count - jbd2_journal_destroy will
>>> iput. */
>>> @@ -1076,7 +1078,7 @@ void ocfs2_journal_shutdown(struct
>>> ocfs2_super *osb)
>>>  
>>>         BUG_ON(atomic_read(&(osb->journal->j_num_trans)) != 0);
>>>  
>>> -       if (ocfs2_mount_local(osb)) {
>>> +       if (ocfs2_mount_local(osb) && state ==
>>> OCFS2_JOURNAL_LOADED) {
>>
>> The only intent of the new introduced state is to identify if journal
>> is
>> truly loaded or not.
>> So it seems that the simplest way to fix this is just check
>> JBD2_LOADED
>> here.
>>
>> if (ocfs2_mount_local(osb) &&
>>     (journal->j_journal->j_flags & JBD2_LOADED)) {
>>         ...
>> }
> Hi, Joseph, thanks for your review and comments. 
> 
> Yeah! It's absolutely the simplest and cleanest way to fix this issue.
> Thanks for your suggestion.
>>
>> BTW, could you please also replace 'osb->journal->j_num_trans' to
>> 'journal->j_num_trans'?
> Sure.
>>
>>>                 jbd2_journal_lock_updates(journal->j_journal);
>>>                 status = jbd2_journal_flush(journal->j_journal, 0);
>>>                 jbd2_journal_unlock_updates(journal->j_journal);
>>> @@ -1174,6 +1176,7 @@ int ocfs2_journal_load(struct ocfs2_journal
>>> *journal, int local, int replayed)
>>>                 }
>>>         } else
>>>                 osb->commit_task = NULL;
>>> +       journal->j_state = OCFS2_JOURNAL_LOADED;
>>
>> It seems that this has to be moved just after jbd2_journal_load().
>> Anyway, I don't think we have to introduce a new state. See above.
>>
> Agreed. And now OCFS2_JOURNAL_LOADED is set when ocfs2_journal_init()
> succeed, it may led to some misunderstanding: the journal was not
> really loaded when OCFS2_JOURNAL_LOADED was set. I would like to rename
> it to OCFS2_JOURNAL_INITED in another patch to make it clearer.

Umm... You can treat it as ocfs2 journal state only, not jbd2.
Also jbd2 doesn't have 'initialized' state either.
So I don't think we have to do this change in the fix.

Joseph  

  reply	other threads:[~2024-08-30 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240823083150.17590-1-sunjunchao2870@gmail.com>
2024-08-30  9:40 ` Joseph Qi
2024-08-30 10:11   ` Julian Sun
2024-08-30 10:58     ` Joseph Qi [this message]
2024-08-30 11:22       ` Julian Sun

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=fe86da76-555d-424a-828f-ea99b05b363f@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=heming.zhao@suse.com \
    --cc=lbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=sunjunchao2870@gmail.com \
    --cc=syzbot+05b9b39d8bdfe1a0861f@syzkaller.appspotmail.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®