From: syzbot <syzbot+d87dd8e018fd2cc2528b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com,
dhowells@redhat.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
npiggin@gmail.com, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: [syzbot] kernel BUG in __tlb_remove_page_size (2)
Date: Tue, 07 Feb 2023 06:31:17 -0800 [thread overview]
Message-ID: <00000000000025e37805f41d0049@google.com> (raw)
In-Reply-To: <3151379.1675779370@warthog.procyon.org.uk>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P5549 } 2638 jiffies s: 2817 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: fab9eebf iov_iter: Kill ITER_PIPE
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/ iov-fixes
console output: https://syzkaller.appspot.com/x/log.txt?x=14e2c6f3480000
kernel config: https://syzkaller.appspot.com/x/.config?x=facc234423e66dc6
dashboard link: https://syzkaller.appspot.com/bug?extid=d87dd8e018fd2cc2528b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
next prev parent reply other threads:[~2023-02-07 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 13:36 [syzbot] kernel BUG in __tlb_remove_page_size (2) syzbot
2023-02-07 14:16 ` David Howells
2023-02-07 14:31 ` syzbot [this message]
[not found] <20230205072452.1229-1-hdanton@sina.com>
2023-02-05 7:40 ` syzbot
[not found] <20230205082542.1363-1-hdanton@sina.com>
2023-02-05 8:53 ` syzbot
[not found] <20230205094432.1510-1-hdanton@sina.com>
2023-02-05 10:33 ` syzbot
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=00000000000025e37805f41d0049@google.com \
--to=syzbot+d87dd8e018fd2cc2528b@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.