linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, aryabinin@virtuozzo.com, bp@alien8.de,
	 cai@lca.pw, clm@fb.com, dan.carpenter@oracle.com,
	dave@stgolabs.net,  dhowells@redhat.com, dsterba@suse.com,
	dsterba@suse.cz, dvyukov@google.com,  ebiederm@xmission.com,
	glider@google.com, hpa@zytor.com, jbacik@fb.com,
	 ktkhai@virtuozzo.com, ktsanaktsidis@zendesk.com,
	linux-btrfs@vger.kernel.org,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, manfred@colorfullife.com,  mhocko@suse.com,
	mingo@redhat.com, nborisov@suse.com,
	 penguin-kernel@I-love.SAKURA.ne.jp,
	penguin-kernel@i-love.sakura.ne.jp,  rppt@linux.vnet.ibm.com,
	sfr@canb.auug.org.au, shakeelb@google.com,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	 torvalds@linux-foundation.org, vdavydov.dev@gmail.com,
	willy@infradead.org
Subject: Re: general protection fault in put_pid
Date: Thu, 07 Nov 2019 05:42:09 -0800	[thread overview]
Message-ID: <000000000000fbc9650596c1d456@google.com> (raw)
In-Reply-To: <00000000000051ee78057cc4d98f@google.com>

syzbot suspects this bug was fixed by commit:

commit a8e911d13540487942d53137c156bd7707f66e5d
Author: Qian Cai <cai@lca.pw>
Date:   Fri Feb 1 22:20:20 2019 +0000

     x86_64: increase stack size for KASAN_EXTRA

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10364f3c600000
start commit:   f5d58277 Merge branch 'for-linus' of git://git.kernel.org/..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
dashboard link: https://syzkaller.appspot.com/bug?extid=1145ec2e23165570c3ac
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16803afb400000

If the result looks correct, please mark the bug fixed by replying with:

#syz fix: x86_64: increase stack size for KASAN_EXTRA

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


      parent reply	other threads:[~2019-11-07 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00000000000051ee78057cc4d98f@google.com>
2019-03-27 20:10 ` general protection fault in put_pid syzbot
2019-03-27 20:27   ` Matthew Wilcox
2019-03-27 22:51     ` David Sterba
2019-11-07 13:42 ` syzbot [this message]

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=000000000000fbc9650596c1d456@google.com \
    --to=syzbot+1145ec2e23165570c3ac@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=bp@alien8.de \
    --cc=cai@lca.pw \
    --cc=clm@fb.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dave@stgolabs.net \
    --cc=dhowells@redhat.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=glider@google.com \
    --cc=hpa@zytor.com \
    --cc=jbacik@fb.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=ktsanaktsidis@zendesk.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=manfred@colorfullife.com \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=nborisov@suse.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=shakeelb@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vdavydov.dev@gmail.com \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).