From: syzbot <syzbot+c39682e86c9d84152f93@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in static_key_slow_inc (2)
Date: Wed, 02 Nov 2022 11:14:25 -0700 [thread overview]
Message-ID: <00000000000088962f05ec80cf2b@google.com> (raw)
In-Reply-To: <20221102135324.3935-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
kernel/cgroup/legacy_freezer.c:353:35: error: passing argument 1 of 'static_key_slow_inc_cpuslocked' from incompatible pointer type [-Werror=incompatible-pointer-types]
kernel/cgroup/legacy_freezer.c:364:36: error: passing argument 1 of 'static_key_slow_dec_cpuslocked' from incompatible pointer type [-Werror=incompatible-pointer-types]
kernel/cgroup/legacy_freezer.c:382:2: error: implicit declaration of function 'cpus_read_lock'; did you mean 'rcu_read_lock'? [-Werror=implicit-function-declaration]
kernel/cgroup/legacy_freezer.c:411:2: error: implicit declaration of function 'cpus_read_unlock'; did you mean 'rcu_read_unlock'? [-Werror=implicit-function-declaration]
Tested on:
commit: a2c65a9d net: dsa: fall back to default tagger if we c..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
dashboard link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=127fa2ca880000
next parent reply other threads:[~2022-11-02 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221102135324.3935-1-hdanton@sina.com>
2022-11-02 18:14 ` syzbot [this message]
[not found] <20221103120829.504-1-hdanton@sina.com>
2022-11-03 12:33 ` [syzbot] possible deadlock in static_key_slow_inc (2) syzbot
[not found] <20221103001520.4011-1-hdanton@sina.com>
2022-11-03 11:21 ` syzbot
2022-11-02 10:36 syzbot
2022-11-02 10:36 ` 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=00000000000088962f05ec80cf2b@google.com \
--to=syzbot+c39682e86c9d84152f93@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 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.