Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1720249

Re: WARNING: possible circular locking dependency detected

From Thomas Gleixner <tglx@linutronix.de>
Newsgroups linux.kernel
Subject Re: WARNING: possible circular locking dependency detected
Date 2017-08-25 18:30 +0200
Message-ID <uipEC-6ki-13@gated-at.bofh.it> (permalink)
References <uijIS-2Ic-11@gated-at.bofh.it> <uio5Q-5gL-7@gated-at.bofh.it> <uipuW-6gP-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Sat, 26 Aug 2017, Byungchul Park wrote:
> On Fri, Aug 25, 2017 at 11:47 PM, Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
> > We hold the sparse_irq_lock lock while waiting for the completion in the
> > CPU-down case and in the CPU-up case we acquire the sparse_irq_lock lock
> > while the other CPU is waiting for the completion.
> > This is not an issue if my interpretation of lockdep here is correct.
> 
> Hello Sebastian,
> 
> I think you parsed the message correctly.
> 
> The message is saying that, for example:
> 
> context A (maybe being up?)
> --
> lock(sparse_irq_lock) // wait for sparse_irq_lock in B to be released
> complete(st->done) // impossible to hit here
> 
> context B (maybe wanting to synchronize with the cpu being up?)
> --
> lock(sparse_irq_lock) // acquired successfully
> wait_for_completion(st->done) // wait for completion of st->done in A
> unlock(sparse_irq_lock) // impossible to hit here
> 
> I cannot check the kernel code at the moment.. I wonder if this scenario is
> impossible. Could you answer it?

Yes, it's impossible because cpu hotplug is globally serialized. So the cpu
down scenario cannot happen in parallel with the cpu up scenario.

Thanks,

	tglx

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

WARNING: possible circular locking dependency detected Borislav Petkov <bp@alien8.de> - 2017-08-25 12:10 +0200
  Re: WARNING: possible circular locking dependency detected Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2017-08-25 16:50 +0200
    Re: WARNING: possible circular locking dependency detected Byungchul Park <max.byungchul.park@gmail.com> - 2017-08-25 18:20 +0200
      Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-25 18:30 +0200
    Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-28 09:50 +0200
    Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-28 16:20 +0200
    Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-29 21:40 +0200
  Re: WARNING: possible circular locking dependency detected Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2017-08-25 18:50 +0200
  Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-28 17:00 +0200
    Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-28 17:10 +0200
      Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-28 18:40 +0200
    Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-29 19:50 +0200
      Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-29 21:50 +0200
        Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-29 22:20 +0200
          Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-30 07:50 +0200
            Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-31 09:10 +0200
              Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-31 09:40 +0200
                Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-31 10:00 +0200
                Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-08-31 10:10 +0200
                Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-31 10:20 +0200
                Re: WARNING: possible circular locking dependency detected Thomas Gleixner <tglx@linutronix.de> - 2017-08-31 23:30 +0200
                Re: WARNING: possible circular locking dependency detected Peter Zijlstra <peterz@infradead.org> - 2017-09-01 22:40 +0200

csiph-web