mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: iommu@lists.linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommu/vt-d: Don't register bus-notifier under
Date: Tue, 10 Oct 2017 09:21:41 +0200	[thread overview]
Message-ID: <20171010072141.57vbnmg4crpsk6ip@suse.de> (raw)
In-Reply-To: <2ee59dfe-0a02-05b6-8115-5846b49bc053@siemens.com>

On Mon, Oct 09, 2017 at 06:58:13PM +0200, Jan Kiszka wrote:
> >  extern int dmar_table_init(void);
> >  extern int dmar_dev_scope_init(void);
> > +extern void dmar_register_bus_notifier(void);
> >  extern int dmar_parse_dev_scope(void *start, void *end, int *cnt,
> >  				struct dmar_dev_scope **devices, u16 segment);
> >  extern void *dmar_alloc_dev_scope(void *start, void *end, int *cnt);
> > 
> 
> Silences the warning, but locking in the init paths still smells fishy
> to me.

Yes, its certainly not optimal, but the code that runs in there also
runs at iommu hotplug time, so we can't just remove the locking there
entirely.

On the other side the warning you reported is a false-positive, it can
never dead-lock because the reverse lock-order happens only at
initialization time, but I don't know how to silence it otherwise.


Regards,

	Joerg

  reply	other threads:[~2017-10-10  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 12:14 intel-dmar: possible circular locking dependency detected Jan Kiszka
2017-09-27 13:21 ` Jan Kiszka
2017-09-27 14:19   ` Jan Kiszka
2017-09-28 13:41     ` Joerg Roedel
2017-10-06 13:08     ` [PATCH] iommu/vt-d: Don't register bus-notifier under Joerg Roedel
2017-10-09 16:58       ` Jan Kiszka
2017-10-10  7:21         ` Joerg Roedel [this message]
2017-10-10  7:24           ` Jan Kiszka

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=20171010072141.57vbnmg4crpsk6ip@suse.de \
    --to=jroedel@suse.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome