From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Leon Romanovsky <leon@kernel.org>,
syzbot <syzbot+9627a92b1f9262d5d30c@syzkaller.appspotmail.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Rafael Wysocki <rafael@kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING in ib_umad_kill_port
Date: Tue, 7 Apr 2020 08:55:48 -0300 [thread overview]
Message-ID: <20200407115548.GU20941@ziepe.ca> (raw)
In-Reply-To: <CACT4Y+Zv_WXEn6u5a6kRZpkDJnSzeGF1L7JMw4g85TLEgAM7Lw@mail.gmail.com>
On Tue, Apr 07, 2020 at 11:56:30AM +0200, Dmitry Vyukov wrote:
> > I'm not sure what could be done wrong here to elicit this:
> >
> > sysfs group 'power' not found for kobject 'umad1'
> >
> > ??
> >
> > I've seen another similar sysfs related trigger that we couldn't
> > figure out.
> >
> > Hard to investigate without a reproducer.
>
> Based on all of the sysfs-related bugs I've seen, my bet would be on
> some races. E.g. one thread registers devices, while another
> unregisters these.
I did check that the naming is ordered right, at least we won't be
concurrently creating and destroying umadX sysfs of the same names.
I'm also fairly sure we can't be destroying the parent at the same
time as this child.
Do you see the above commonly? Could it be some driver core thing? Or
is it more likely something wrong in umad?
Jason
next prev parent reply other threads:[~2020-04-07 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 6:37 WARNING in ib_umad_kill_port syzbot
2020-04-06 17:21 ` Leon Romanovsky
2020-04-06 17:44 ` Jason Gunthorpe
2020-04-07 9:56 ` Dmitry Vyukov
2020-04-07 11:55 ` Jason Gunthorpe [this message]
2020-04-07 12:39 ` Dmitry Vyukov
2020-04-07 14:33 ` Greg Kroah-Hartman
2020-04-07 14:35 ` Jason Gunthorpe
2020-04-09 13:35 ` Dmitry Vyukov
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=20200407115548.GU20941@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzbot+9627a92b1f9262d5d30c@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).