From: syzbot <syzbot+70b97abe3e253d1c3f8e@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jonathan.cameron@huawei.com,
krzysztof.kozlowski@linaro.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, luca@z3ntu.xyz,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel BUG in validate_mm (2)
Date: Sun, 06 Aug 2023 18:49:27 -0700 [thread overview]
Message-ID: <000000000000efbc2306024b74cf@google.com> (raw)
In-Reply-To: <000000000000b35ea205ffc35fe1@google.com>
syzbot suspects this issue was fixed by commit:
commit ef513aa7aa5038d2f53e9f2932af5006f37ed0b6
Author: Luca Weiss <luca@z3ntu.xyz>
Date: Thu Apr 13 23:17:49 2023 +0000
dt-bindings: iio: adc: qcom,spmi-vadc: Allow 1/16 for pre-scaling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11aeb085a80000
start commit: a901a3568fd2 Merge tag 'iomap-6.5-merge-1' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f5e1158c5b2f83bb
dashboard link: https://syzkaller.appspot.com/bug?extid=70b97abe3e253d1c3f8e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1511d490a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130e5cfb280000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: dt-bindings: iio: adc: qcom,spmi-vadc: Allow 1/16 for pre-scaling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-07 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 20:37 [syzbot] [mm?] kernel BUG in validate_mm (2) syzbot
2023-08-07 1:49 ` syzbot [this message]
2023-08-07 12:11 ` Aleksandr Nogikh
2023-08-11 12:10 ` Aleksandr Nogikh
[not found] <20230807103711.1810-1-hdanton@sina.com>
2023-08-07 11:23 ` 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=000000000000efbc2306024b74cf@google.com \
--to=syzbot+70b97abe3e253d1c3f8e@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luca@z3ntu.xyz \
--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