All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Zhang\, Qiang" <Qiang.Zhang@windriver.com>,
	syzbot <syzbot+9f78d5c664a8c33f4cce@syzkaller.appspotmail.com>,
	"davem\@davemloft.net" <davem@davemloft.net>,
	"fweisbec\@gmail.com" <fweisbec@gmail.com>,
	"jhs\@mojatatu.com" <jhs@mojatatu.com>,
	"jiri\@resnulli.us" <jiri@resnulli.us>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mingo\@kernel.org" <mingo@kernel.org>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
	"syzkaller-bugs\@googlegroups.com"
	<syzkaller-bugs@googlegroups.com>,
	"tglx\@linutronix.de" <tglx@linutronix.de>,
	"xiyou.wangcong\@gmail.com" <xiyou.wangcong@gmail.com>
Subject: Re: 回复: INFO: rcu detected stall in tc_modify_qdisc
Date: Thu, 30 Jul 2020 15:01:11 -0700	[thread overview]
Message-ID: <874kpoy860.fsf@intel.com> (raw)
In-Reply-To: <CACT4Y+ZY-JnawN5Tmeh0+EfbsXgcv11QDiE-Lh2t8Cc3L1OEXg@mail.gmail.com>

Dmitry Vyukov <dvyukov@google.com> writes:

>> >
>> > Also are we talking about CAP_NET_ADMIN in a user ns as well
>> > (effectively nobody)?
>>
>> Just checked, we are talking about CAP_NET_ADMIN in user namespace as
>> well.
>
> OK, so this is not root/admin, this is just any user.

Yeah, will fix this.


Thanks,
-- 
Vinicius

      reply	other threads:[~2020-07-30 22:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  5:53 INFO: rcu detected stall in tc_modify_qdisc syzbot
2020-07-29  7:28 ` 回复: " Zhang, Qiang
2020-07-29 19:13   ` Vinicius Costa Gomes
2020-07-30  5:58     ` Dmitry Vyukov
2020-07-30 17:44       ` Vinicius Costa Gomes
2020-07-30 18:36         ` Eric Dumazet
2020-07-30 21:01           ` Vinicius Costa Gomes
2020-07-30 19:19         ` Dmitry Vyukov
2020-07-30 22:01           ` Vinicius Costa Gomes [this message]

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=874kpoy860.fsf@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=Qiang.Zhang@windriver.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+9f78d5c664a8c33f4cce@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=xiyou.wangcong@gmail.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.