public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+604424eb051c2f696163@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [PATCH] Test oob in squashfs readahead
Date: Mon, 13 Nov 2023 16:22:46 -0800	[thread overview]
Message-ID: <000000000000308657060a11c90b@google.com> (raw)
In-Reply-To: <000000000000b1fda20609ede0d1@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test oob in squashfs readahead
Author: eadavis@qq.com

please test squashfs readahead oob

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 13d88ac54ddd

diff --git a/fs/squashfs/file.c b/fs/squashfs/file.c
index 8ba8c4c50770..cb3753782d85 100644
--- a/fs/squashfs/file.c
+++ b/fs/squashfs/file.c
@@ -566,6 +566,8 @@ static void squashfs_readahead(struct readahead_control *ractl)
 
 		max_pages = (expected + PAGE_SIZE - 1) >> PAGE_SHIFT;
 
+		if (!max_pages)
+			break;
 		nr_pages = __readahead_batch(ractl, pages, max_pages);
 		if (!nr_pages)
 			break;


  parent reply	other threads:[~2023-11-14  0:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  5:32 [syzbot] [squashfs?] KASAN: slab-out-of-bounds Write in squashfs_readahead (2) syzbot
2023-11-13 11:00 ` [syzbot] [PATCH] Test oob in squashfs readahead syzbot
2023-11-13 12:10 ` syzbot
2023-11-13 15:27 ` [syzbot] [squashfs?] KASAN: slab-out-of-bounds Write in squashfs_readahead (2) Phillip Lougher
2023-11-14  0:22 ` syzbot [this message]
2023-11-14  1:04 ` [syzbot] [PATCH] Test oob in squashfs readahead syzbot
2023-11-14  1:55 ` syzbot
2023-11-14  3:33 ` syzbot
2023-11-14  4:06 ` syzbot
2023-11-14  6:35 ` syzbot
2023-11-14  7:53 ` syzbot
2023-11-14  8:58 ` syzbot
2023-11-15  2:21 ` syzbot
     [not found] ` <tencent_35864B36740976B766CA3CC936A496AA3609@qq.com>
2023-11-15 22:39   ` [PATCH] squashfs: fix oob in squashfs_readahead Andrew Morton
2023-11-16 15:14   ` Phillip Lougher
2023-11-17 13:17   ` Marek Szyprowski
2023-11-17 15:48     ` 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=000000000000308657060a11c90b@google.com \
    --to=syzbot+604424eb051c2f696163@syzkaller.appspotmail.com \
    --cc=linux-kernel@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