From: Barry Song <21cnbao@gmail.com>
To: Nhat Pham <nphamcs@gmail.com>
Cc: syzbot <syzbot+adbc983a1588b7805de3@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, chengming.zhou@linux.dev,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
yosryahmed@google.com, Barry Song <v-songbaohua@oppo.com>
Subject: Re: [syzbot] [mm?] kernel BUG in sg_init_one
Date: Tue, 19 Mar 2024 09:25:09 +1300 [thread overview]
Message-ID: <CAGsJ_4y7aFg3FBh_isa_TCqY1B8n64Rro5mVu6=wvk7FP35mWw@mail.gmail.com> (raw)
In-Reply-To: <CAKEwX=MAX0km1p43DQmKbeSy2G4dPFHiF+deH_qzqygc2Vnjig@mail.gmail.com>
On Tue, Mar 19, 2024 at 7:00 AM Nhat Pham <nphamcs@gmail.com> wrote:
>
> On Mon, Mar 18, 2024 at 9:58 AM syzbot
> <syzbot+adbc983a1588b7805de3@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: e5eb28f6d1af Merge tag 'mm-nonmm-stable-2024-03-14-09-36' ..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=13043abe180000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=19bb57c23dffc38e
> > dashboard link: https://syzkaller.appspot.com/bug?extid=adbc983a1588b7805de3
> > compiler: arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> > userspace arch: arm
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1706d231180000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ba7959180000
> >
> > Downloadable assets:
> > disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/8ead8862021c/non_bootable_disk-e5eb28f6.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/0a7371c63ff2/vmlinux-e5eb28f6.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/7539441b4add/zImage-e5eb28f6.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+adbc983a1588b7805de3@syzkaller.appspotmail.com
> >
> > ------------[ cut here ]------------
> > kernel BUG at include/linux/scatterlist.h:187!
>
> Looks like the provided buffer is invalid:
>
> #ifdef CONFIG_DEBUG_SG
> BUG_ON(!virt_addr_valid(buf));
> #endif
>
> which is "src" from:
>
> sg_init_one(&input, src, entry->length);
>
> Looking at the surrounding code and recent history, there's this
> commit that stands out:
>
> mm/zswap: remove the memcpy if acomp is not sleepable
> (sha: 270700dd06ca41a4779c19eb46608f076bb7d40e)
>
> which has the effect of, IIUC, using the zpool mapped memory directly
> as src, instead of acomp_ctx->buffer (which was previously the case,
> as zsmalloc was not sleepable).
>
> This might not necessarily be a bug with that commit itself, but might
> have revealed another bug elsewhere.
>
> Anyway, cc-ing the author, Barry Song, to fact check me :) Will take a
> closer look later.
I guess that is because on arm32 , we have highmem but
sg_init_one supports lowmem only. the below should be
able to fix?
diff --git a/mm/zswap.c b/mm/zswap.c
index 9dec853647c8..47c0386caba2 100644
--- a/mm/zswap.c
+++ b/mm/zswap.c
@@ -1086,7 +1086,8 @@ static void zswap_decompress(struct zswap_entry
*entry, struct page *page)
zpool_unmap_handle(zpool, entry->handle);
}
- sg_init_one(&input, src, entry->length);
+ sg_init_table(&input, 1);
+ sg_set_page(&input, kmap_to_page(src), entry->length,
offset_in_page(src));
sg_init_table(&output, 1);
sg_set_page(&output, page, PAGE_SIZE, 0);
acomp_request_set_params(acomp_ctx->req, &input, &output,
entry->length, PAGE_SIZE);
>
next prev parent reply other threads:[~2024-03-18 20:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 16:58 syzbot
2024-03-18 18:00 ` Nhat Pham
2024-03-18 20:17 ` Yosry Ahmed
2024-03-18 21:09 ` Johannes Weiner
2024-03-18 21:15 ` Barry Song
2024-03-18 21:32 ` Johannes Weiner
2024-03-18 21:37 ` Barry Song
2024-03-18 21:18 ` Yosry Ahmed
2024-03-18 21:21 ` Barry Song
2024-03-18 20:25 ` Barry Song [this message]
2024-03-18 20:34 ` Yosry Ahmed
2024-03-18 20:50 ` Barry Song
2024-03-18 20:59 ` Yosry Ahmed
2024-03-18 21:12 ` Barry Song
2024-03-18 20:42 ` Barry Song
2024-03-18 20:52 ` syzbot
2024-03-18 21:03 ` Barry Song
2025-02-12 17:20 ` Yosry Ahmed
2025-02-22 0:48 ` Yosry Ahmed
2025-02-26 16:01 ` Ira Weiny
2025-02-26 16:45 ` Yosry Ahmed
2025-02-26 20:36 ` Ira Weiny
2024-03-18 22:27 ` Barry Song
2024-03-18 22:52 ` syzbot
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='CAGsJ_4y7aFg3FBh_isa_TCqY1B8n64Rro5mVu6=wvk7FP35mWw@mail.gmail.com' \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=syzbot+adbc983a1588b7805de3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v-songbaohua@oppo.com \
--cc=yosryahmed@google.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