linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Edward Adam Davis <eadavis@qq.com>
Cc: jfs-discussion@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+bba84aef3a26fb93deb9@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH V2] jfs: fix null ptr deref in dtInsertEntry
Date: Wed, 26 Jun 2024 12:30:07 -0500	[thread overview]
Message-ID: <455b4ee7-7fa8-4f1c-9711-6ebf583519e2@oracle.com> (raw)
In-Reply-To: <tencent_4AA6ED5ECD6879FE6FD02EFD6D109638E80A@qq.com>

Finally catching up on some neglected patches.

Looks good to me. Applied.

Shaggy

On 4/11/24 7:05AM, Edward Adam Davis wrote:
> [syzbot reported]
> general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI
> KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
> CPU: 0 PID: 5061 Comm: syz-executor404 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
> RIP: 0010:dtInsertEntry+0xd0c/0x1780 fs/jfs/jfs_dtree.c:3713
> ...
> [Analyze]
> In dtInsertEntry(), when the pointer h has the same value as p, after writing
> name in UniStrncpy_to_le(), p->header.flag will be cleared. This will cause the
> previously true judgment "p->header.flag & BT-LEAF" to change to no after writing
> the name operation, this leads to entering an incorrect branch and accessing the
> uninitialized object ih when judging this condition for the second time.
> 
> [Fix]
> After got the page, check freelist first, if freelist == 0 then exit dtInsert()
> and return -EINVAL.
> 
> Reported-by: syzbot+bba84aef3a26fb93deb9@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
>   fs/jfs/jfs_dtree.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/fs/jfs/jfs_dtree.c b/fs/jfs/jfs_dtree.c
> index 031d8f570f58..5d3127ca68a4 100644
> --- a/fs/jfs/jfs_dtree.c
> +++ b/fs/jfs/jfs_dtree.c
> @@ -834,6 +834,8 @@ int dtInsert(tid_t tid, struct inode *ip,
>   	 * the full page.
>   	 */
>   	DT_GETSEARCH(ip, btstack->top, bn, mp, p, index);
> +	if (p->header.freelist == 0)
> +		return -EINVAL;
>   
>   	/*
>   	 *	insert entry for new key

      reply	other threads:[~2024-06-26 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  6:22 [syzbot] [jfs?] general protection fault in dtInsertEntry syzbot
2024-04-10  7:05 ` [PATCH] jfs: reserve the header and use freelist from second Edward Adam Davis
2024-04-10 16:58   ` [Jfs-discussion] " Dave Kleikamp
2024-04-11 12:05     ` [PATCH V2] jfs: fix null ptr deref in dtInsertEntry Edward Adam Davis
2024-06-26 17:30       ` Dave Kleikamp [this message]

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=455b4ee7-7fa8-4f1c-9711-6ebf583519e2@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=eadavis@qq.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+bba84aef3a26fb93deb9@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;
as well as URLs for NNTP newsgroup(s).