public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in do_mkdirat
Date: Fri, 09 Dec 2022 23:24:21 -0800	[thread overview]
Message-ID: <000000000000b133c805ef74280a@google.com> (raw)
In-Reply-To: <20221210011440.2050-1-hdanton@sina.com>

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: { P4107 } 2635 jiffies s: 2829 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):


Tested on:

commit:         0d1409e4 Merge tag 'drm-fixes-2022-12-09' of git://ano..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14f4750b880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d58e7fe7f9cf5e24
dashboard link: https://syzkaller.appspot.com/bug?extid=919c5a9be8433b8bf201
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1070ffdf880000


       reply	other threads:[~2022-12-10  7:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221210011440.2050-1-hdanton@sina.com>
2022-12-10  7:24 ` syzbot [this message]
     [not found] <20221215235133.1097-1-hdanton@sina.com>
2022-12-16  7:53 ` [syzbot] WARNING in do_mkdirat syzbot
     [not found] <20221211002908.2210-1-hdanton@sina.com>
2022-12-11  2:30 ` syzbot
2022-12-11  2:52   ` Al Viro
     [not found]   ` <20221211075612.2486-1-hdanton@sina.com>
2022-12-11  8:39     ` Al Viro
     [not found]     ` <20221211102208.2600-1-hdanton@sina.com>
2022-12-11 15:46       ` Matthew Wilcox
2022-12-11 20:54         ` Al Viro
     [not found]       ` <20221212032911.2965-1-hdanton@sina.com>
2022-12-12 18:58         ` Theodore Ts'o
2022-12-12 19:29           ` Marco Elver
2022-12-13  1:44             ` Al Viro
2022-12-16 15:48               ` Aleksandr Nogikh
2022-12-29 21:17                 ` Eric Biggers
2022-12-31 16:57                   ` Theodore Ts'o
2022-12-31 17:03                     ` Randy Dunlap
2023-01-03 13:36                     ` Aleksandr Nogikh
     [not found]         ` <20221213014716.3347-1-hdanton@sina.com>
2022-12-13  3:36           ` Al Viro
     [not found]             ` <20221213041225.3461-1-hdanton@sina.com>
2022-12-13 11:05               ` Alexander Potapenko
2022-12-03 14:52 syzbot
2022-12-09 19:50 ` syzbot
2022-12-09 19:57   ` Matthew Wilcox
2022-12-10 18:06 ` 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=000000000000b133c805ef74280a@google.com \
    --to=syzbot+919c5a9be8433b8bf201@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --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