From: Esme <esploit@protonmail.ch>
To: cai@lca.pw
Cc: jejb@linux.ibm.com, dgilbert@interlog.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL
Date: Thu, 10 Jan 2019 21:10:20 +0000 [thread overview]
Message-ID: <_eAiOKAc5XvXj5oa6DQFgR2W0XgtaPXr4ZjA2_SzH4JpHUjgUajvPd2yOIJr2FIE3g8vrl89S_lrvW0ghMqZlFWYFseLGRu4b5HZggLn3l0=@protonmail.ch> (raw)
In-Reply-To: <1547154231.6911.10.camel@lca.pw>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
The information gathering scripts may have taken my host kernel 4.20) I'll double check from proc/config.g
Sent from ProtonMail mobile
-------- Original Message --------
On Jan 10, 2019, 4:03 PM, Qian Cai wrote:
> On Thu, 2019-01-10 at 20:47 +0000, Esme wrote:
>> Sure thing;
>>
>> cmdline;
>> qemu-system-x86_64 -kernel linux//arch/x86/boot/bzImage -append console=ttyS0
>> root=/dev/sda debug earlyprintk=serial slub_debug=QUZ -hda stretch.img -net
>> user,hostfwd=tcp::10021-:22 -net nic -enable-kvm -nographic -m 2G -smp 2
>> -pidfile
>>
>> CONFIG_PAGE*; (full file attached);
>>
>> # CONFIG_DEBUG_PAGEALLOC is not set
>> CONFIG_PAGE_POISONING=y
>> CONFIG_PAGE_POISONING_NO_SANITY=y
>> # CONFIG_PAGE_POISONING_ZERO is not set
>> # CONFIG_DEBUG_PAGE_REF is not set
>> CONFIG_FAIL_PAGE_ALLOC=y
>
> Confused.
>
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1896410.html
>
> It said 5.0.0-rc1+
>
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1896410/repro.repor
> t
>
> It said 4.20.0+, and it also have,
>
> "general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN PTI"
>
> which indicated CONFIG_DEBUG_PAGEALLOC=y but your .config said NO.
>
> However, it looks like a mess that KASAN does not play well with all those
> SLUB_DEBUG, CONFIG_DEBUG_PAGEALLOC etc, because it essentially step into each
> others' toes by redzoning, poisoning in allocate and free pages.
[-- Attachment #2: Type: text/html, Size: 1935 bytes --]
next prev parent reply other threads:[~2019-01-10 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <t78EEfgpy3uIwPUvqvmuQEYEWKG9avWzjUD3EyR93Qaf_tfx1gqt4XplrqMgdxR1U9SsrVdA7G9XeUZacgUin0n6lBzoxJHVJ9Ko0yzzrxI=@protonmail.ch>
2019-01-10 19:58 ` James Bottomley
2019-01-10 19:58 ` James Bottomley
2019-01-10 20:39 ` Qian Cai
2019-01-10 20:39 ` Qian Cai
2019-01-10 20:44 ` Qian Cai
2019-01-10 20:44 ` Qian Cai
2019-01-10 20:47 ` Esme
2019-01-10 21:03 ` Qian Cai
2019-01-10 21:10 ` Esme [this message]
2019-01-10 21:35 ` Esme
2019-01-10 22:33 ` Qian Cai
2019-01-10 22:58 ` Esme
2019-01-11 1:30 ` Qian Cai
2019-01-11 3:15 ` Esme
2019-01-11 4:52 ` Qian Cai
2019-01-11 5:01 ` Esme
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='_eAiOKAc5XvXj5oa6DQFgR2W0XgtaPXr4ZjA2_SzH4JpHUjgUajvPd2yOIJr2FIE3g8vrl89S_lrvW0ghMqZlFWYFseLGRu4b5HZggLn3l0=@protonmail.ch' \
--to=esploit@protonmail.ch \
--cc=cai@lca.pw \
--cc=dgilbert@interlog.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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