From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shoaib Rao <rao.shoaib@oracle.com>, Eric Dumazet <edumazet@google.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+8760ca6c1ee783ac4abd@syzkaller.appspotmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, bpf <bpf@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Cong Wang <cong.wang@bytedance.com>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
jamorris@linux.microsoft.com,
John Fastabend <john.fastabend@gmail.com>,
Martin KaFai Lau <kafai@fb.com>,
kpsingh@kernel.org, Jakub Kicinski <kuba@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
Song Liu <songliubraving@fb.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>, Yonghong Song <yhs@fb.com>
Subject: Re: [syzbot] BUG: sleeping function called from invalid context in _copy_to_iter
Date: Tue, 10 Aug 2021 11:19:26 +0200 [thread overview]
Message-ID: <66417ce5-a0f0-9012-6c2e-7c8f1b161cff@gmail.com> (raw)
In-Reply-To: <ca6a188a-6ce4-782b-9700-9ae4ac03f83e@oracle.com>
On 8/9/21 10:31 PM, Shoaib Rao wrote:
>
> On 8/9/21 1:09 PM, Eric Dumazet wrote:
>> I am guessing that even your test would trigger the warning,
>> if you make sure to include CONFIG_DEBUG_ATOMIC_SLEEP=y in your kernel build.
>
> Eric,
>
> Thanks for the pointer, have you ever over looked at something when coding?
>
I _think_ I was trying to help, not shaming you in any way.
My question about spinlock/mutex was not sarcastic, you authored
6 official linux patches, there is no evidence for linux kernel expertise.
next prev parent reply other threads:[~2021-08-10 9:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 23:38 [syzbot] BUG: sleeping function called from invalid context in _copy_to_iter syzbot
2021-08-09 17:32 ` Shoaib Rao
2021-08-09 18:06 ` Dmitry Vyukov
2021-08-09 19:16 ` Shoaib Rao
2021-08-09 19:21 ` Dmitry Vyukov
2021-08-09 19:40 ` Shoaib Rao
2021-08-09 20:02 ` Eric Dumazet
2021-08-09 20:09 ` Eric Dumazet
2021-08-09 20:31 ` Shoaib Rao
2021-08-10 9:19 ` Eric Dumazet [this message]
2021-08-10 17:50 ` Shoaib Rao
2021-08-10 18:02 ` Eric Dumazet
2021-08-10 18:29 ` Shoaib Rao
2021-08-09 20:04 ` Al Viro
2021-08-09 20:16 ` Al Viro
2021-08-09 20:30 ` Shoaib Rao
2021-08-09 20:37 ` Shoaib Rao
2021-08-09 21:41 ` Al Viro
2021-08-09 22:38 ` Shoaib Rao
2021-08-09 19:57 ` Al Viro
2021-08-09 20:18 ` Shoaib Rao
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=66417ce5-a0f0-9012-6c2e-7c8f1b161cff@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=cong.wang@bytedance.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=jamorris@linux.microsoft.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rao.shoaib@oracle.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+8760ca6c1ee783ac4abd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yhs@fb.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