From: Shankara Pailoor <sp3485@columbia.edu>
To: LKML <linux-kernel@vger.kernel.org>,
reiserfs-devel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrew Zhu Aday <andrew.aday@columbia.edu>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: Hung Task Linux 4.13-rc7 Reiserfs
Date: Sat, 30 Sep 2017 15:20:25 -0400 [thread overview]
Message-ID: <CAASgV=tjsY1tdxryj_3_TeA_N_SjbXUoUfVd8fu33+dHTx13tw@mail.gmail.com> (raw)
In-Reply-To: <CAASgV=sdweCbYxZRn3RR_gEm5qzyjLRHq+Ctk1vTD0yj5VjjLw@mail.gmail.com>
Hi,
I have a reproducer program. It takes about 3-5 minutes to trigger the
hang. The only calls are mmap, open, write, and readahead and the
writes are fairly small (512 bytes).
Reproducer Program: https://pastebin.com/cx1cgABc
Report: https://pastebin.com/uGTAw45E
Logs: https://pastebin.com/EaiE0JLf
Kernel Configs: https://pastebin.com/i6URdADw
Regards,
Shankara
On Fri, Sep 29, 2017 at 11:56 PM, Shankara Pailoor <sp3485@columbia.edu> wrote:
> Hi,
>
> I am fuzzing the kernel 4.13-rc7 with Syzkaller with Reiserfs. I am
> getting the following crash:
>
> INFO: task kworker/0:3:1103 blocked for more than 120 seconds.
>
>
> Here is the full stack trace. I noticed that there are a few tasks
> holding a sbi->lock. Below are a report and a log of all the programs
> executing at the time of the incident.
>
>
> Report: https://pastebin.com/uGTAw45E
> Logs: https://pastebin.com/EaiE0JLf
> Kernel Configs: https://pastebin.com/i6URdADw
>
> I don't have a reproducer yet and any assistance would be appreciated.
>
> Regards,
> Shankara
--
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>
parent reply other threads:[~2017-09-30 19:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAASgV=sdweCbYxZRn3RR_gEm5qzyjLRHq+Ctk1vTD0yj5VjjLw@mail.gmail.com>]
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='CAASgV=tjsY1tdxryj_3_TeA_N_SjbXUoUfVd8fu33+dHTx13tw@mail.gmail.com' \
--to=sp3485@columbia.edu \
--cc=andrew.aday@columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller@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