linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+1505c80c74256c6118a5@syzkaller.appspotmail.com>
To: airlied@linux.ie, akpm@linux-foundation.org, amir73il@gmail.com,
	 chris@chris-wilson.co.uk, darrick.wong@oracle.com,
	david@fromorbit.com,  dri-devel@lists.freedesktop.org,
	dvyukov@google.com, eparis@redhat.com,  hannes@cmpxchg.org,
	hughd@google.com, intel-gfx@lists.freedesktop.org,  jack@suse.cz,
	jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
	 jrdr.linux@gmail.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,  mingo@redhat.com, mszeredi@redhat.com,
	penguin-kernel@I-love.SAKURA.ne.jp,  peterz@infradead.org,
	rodrigo.vivi@intel.com, syzkaller-bugs@googlegroups.com,
	 viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: INFO: rcu detected stall in sys_sendfile64 (2)
Date: Mon, 11 Mar 2019 20:59:00 -0700	[thread overview]
Message-ID: <0000000000008c75b50583ddb5f8@google.com> (raw)
In-Reply-To: <00000000000010b2fc057fcdfaba@google.com>

syzbot has bisected this bug to:

commit 34e07e42c55aeaa78e93b057a6664e2ecde3fadb
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Feb 8 10:54:48 2018 +0000

     drm/i915: Add missing kerneldoc for 'ent' in i915_driver_init_early

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13220283200000
start commit:   34e07e42 drm/i915: Add missing kerneldoc for 'ent' in i915..
git tree:       upstream
final crash:    https://syzkaller.appspot.com/x/report.txt?x=10a20283200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17220283200000
kernel config:  https://syzkaller.appspot.com/x/.config?x=abc3dc9b7a900258
dashboard link: https://syzkaller.appspot.com/bug?extid=1505c80c74256c6118a5
userspace arch: amd64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12c4dc28c00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15df4108c00000

Reported-by: syzbot+1505c80c74256c6118a5@syzkaller.appspotmail.com
Fixes: 34e07e42 ("drm/i915: Add missing kerneldoc for 'ent' in  
i915_driver_init_early")


  parent reply	other threads:[~2019-03-12  3:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19 11:32 syzbot
2019-01-19 11:32 ` syzbot
2019-01-19 11:41 ` Dmitry Vyukov
2019-01-19 11:41   ` Dmitry Vyukov
2019-01-19 13:00   ` Tetsuo Handa
2019-03-12  3:59 ` syzbot [this message]
2019-03-12  4:08   ` Al Viro
2019-03-12  8:00     ` Jani Nikula
2019-03-12 17:10     ` Dmitry Vyukov

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=0000000000008c75b50583ddb5f8@google.com \
    --to=syzbot+1505c80c74256c6118a5@syzkaller.appspotmail.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dvyukov@google.com \
    --cc=eparis@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jack@suse.cz \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=jrdr.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=mszeredi@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=peterz@infradead.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --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