From: Eric Biggers <ebiggers3@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot
<bot+428944d1a848e9d7464aa96da32ba353cc812457@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel paging request in hmac_init_tfm
Date: Thu, 21 Dec 2017 20:27:51 -0600 [thread overview]
Message-ID: <20171222022751.GA26818@zzz.localdomain> (raw)
In-Reply-To: <CACT4Y+bRD5C=ffgOBZNCVFNheH=W304CVRzyGr1FB3W=aYuBNA@mail.gmail.com>
On Thu, Dec 21, 2017 at 08:44:03AM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote:
> On Thu, Dec 21, 2017 at 12:09 AM, Eric Biggers <ebiggers3@gmail.com> wrote:
> > On Mon, Dec 18, 2017 at 11:36:01AM -0800, syzbot wrote:
> >> Hello,
> >>
> >> syzkaller hit the following crash on
> >> 6084b576dca2e898f5c101baef151f7bfdbb606d
> >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> >> compiler: gcc (GCC) 7.1.1 20170620
> >> .config is attached
> >
> > FYI, in linux-next KASAN and other memory debugging options are now behind
> > CONFIG_DEBUG_MEMORY. So, I think KASAN isn't getting turned on anymore, despite
> > the CONFIG_KASAN=y. (Patch was "lib/: make "Memory Debugging" a menuconfig to
> > ease disabling it all".)
>
> Ouch! That would be pretty bad.
>
> But I've tried both linux-next HEAD at:
>
> commit 0e08c463db387a2adcb0243b15ab868a73f87807 (HEAD, tag:
> next-20171221, linux-next/master)
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu Dec 21 15:37:39 2017 +1100
> Add linux-next specific files for 20171221
>
> and mmots HEAD at:
>
> commit 75aa5540627fdb3d8f86229776ea87f995275351 (HEAD, tag:
> v4.15-rc4-mmots-2017-12-20-19-10, mmots/master)
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Thu Dec 21 04:02:17 2017 +0000
> pci: test for unexpectedly disabled bridges
>
> and after running make olddefconfig I still see CONFIG_KASAN=y in
> .config, nor I can find CONFIG_DEBUG_MEMORY in menuconfig.
>
> What am I missing? What commit has added the config?
>
Ah, I see the patch was added to -mm on 2017-12-12 but removed two days later:
https://www.spinics.net/lists/mm-commits/msg129685.html
https://www.spinics.net/lists/mm-commits/msg129696.html
So it was in linux-next temporarily (including the kernel version used for this
particular bug report) but now it's not. Just keep an eye out for it coming
back, I guess.
Eric
next prev parent reply other threads:[~2017-12-22 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94eb2c0d010ad8f1660560a275fd@google.com>
2017-12-20 23:09 ` BUG: unable to handle kernel paging request in hmac_init_tfm Eric Biggers
2017-12-21 7:44 ` Dmitry Vyukov
2017-12-22 2:27 ` Eric Biggers [this message]
2017-12-22 9:01 ` Dmitry Vyukov
2017-12-20 23:42 ` Eric Biggers
2018-01-30 21:41 ` Eric Biggers
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=20171222022751.GA26818@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+428944d1a848e9d7464aa96da32ba353cc812457@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).