From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot
<bot+980f5e5fc060c37505bd65abb49a963518b269d9@syzkaller.appspotmail.com>,
ak@linux.intel.com, akpm@linux-foundation.org, jack@suse.cz,
jlayton@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@techsingularity.net,
mingo@kernel.org, npiggin@gmail.com, rgoldwyn@suse.com,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in filemap_fault
Date: Tue, 19 Dec 2017 07:19:45 +0900 [thread overview]
Message-ID: <b434ed3e-c066-9618-96ca-fd66a362a4fe@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <82d89066-7dd2-12fe-3cc0-c8d624fe0d51@I-love.SAKURA.ne.jp>
On 2017/12/18 23:52, Tetsuo Handa wrote:
> On 2017/12/18 17:43, 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
>> Raw console output is attached.
>>
>> Unfortunately, I don't have any reproducer for this bug yet.
>>
>
> This log has a lot of mmap() but also has Android's binder messages.
>
> r9 = syz_open_dev$binder(&(0x7f0000000000)='/dev/binder#\x00', 0x0, 0x800)
>
> [ 49.200735] binder: 9749:9755 IncRefs 0 refcount change on invalid ref 2 ret -22
> [ 49.221514] binder: 9749:9755 Acquire 1 refcount change on invalid ref 4 ret -22
> [ 49.233325] binder: 9749:9755 Acquire 1 refcount change on invalid ref 0 ret -22
> [ 49.241979] binder: binder_mmap: 9749 205a3000-205a7000 bad vm_flags failed -1
> [ 49.256949] binder: 9749:9755 unknown command 0
> [ 49.262470] binder: 9749:9755 ioctl c0306201 20000fd0 returned -22
> [ 49.293365] binder: 9749:9755 IncRefs 0 refcount change on invalid ref 2 ret -22
> [ 49.301297] binder: binder_mmap: 9749 205a3000-205a7000 bad vm_flags failed -1
> [ 49.314146] binder: 9749:9755 Acquire 1 refcount change on invalid ref 4 ret -22
> [ 49.322732] binder: 9749:9755 Acquire 1 refcount change on invalid ref 0 ret -22
> [ 49.332063] binder: 9749:9755 Release 1 refcount change on invalid ref 1 ret -22
> [ 49.340796] binder: 9749:9755 Acquire 1 refcount change on invalid ref 2 ret -22
> [ 49.349457] binder: 9749:9755 BC_DEAD_BINDER_DONE 0000000000000001 not found
> [ 49.349462] binder: 9749:9755 BC_DEAD_BINDER_DONE 0000000000000000 not found
>
> [ 246.752088] INFO: task syz-executor7:10280 blocked for more than 120 seconds.
>
> Anything that hung after uptime > 46.75 can be reported at uptime = 246.75, can't it?
Typo. I wanted to say 126.75 >= uptime > 6.75.
khungtaskd warning with 120 seconds check interval can be delayed for up to 240 seconds.
>
> Is it possible to reproduce this problem by running the same program?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-18 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 8:43 INFO: task hung in filemap_fault syzbot
2017-12-18 14:52 ` Tetsuo Handa
2017-12-18 22:19 ` Tetsuo Handa [this message]
2017-12-28 14:09 ` Dmitry Vyukov
2018-01-01 15:27 ` Tetsuo Handa
2018-01-08 9:08 ` Dmitry Vyukov
2018-01-08 10:48 ` Tetsuo Handa
2018-01-15 9:40 ` Dmitry Vyukov
2018-01-15 10:44 ` Tetsuo Handa
2018-01-15 12:29 ` Dmitry Vyukov
2018-01-15 13:43 ` Dmitry Vyukov
2018-01-15 13:56 ` Tetsuo Handa
2018-01-15 14:00 ` Dmitry Vyukov
2018-01-15 14:25 ` Tetsuo Handa
2018-01-15 14:27 ` Dmitry Vyukov
2018-01-15 14:38 ` Tetsuo Handa
2018-01-08 9:17 ` 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=b434ed3e-c066-9618-96ca-fd66a362a4fe@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bot+980f5e5fc060c37505bd65abb49a963518b269d9@syzkaller.appspotmail.com \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=rgoldwyn@suse.com \
--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).