[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180321185001.GB11249@infradead.org>
Date: Wed, 21 Mar 2018 11:50:01 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
linux-scsi@...r.kernel.org,
Daniel Bristot de Oliveira <daniel@...stot.me>,
Luis Claudio R. Gonçalves
<lclaudio@...hat.com>, Clark Williams <williams@...hat.com>,
target-devel@...r.kernel.org
Subject: Re: [PATCH] target: Use WARNON_NON_RT(!irqs_disabled())
On Wed, Mar 21, 2018 at 12:38:54PM -0300, Arnaldo Carvalho de Melo wrote:
> assert_spin_locked(&cmd->t_state_lock);
> - WARN_ON_ONCE(!irqs_disabled());
> + WARN_ON_ONCE_NONRT(!irqs_disabled());
I can't find where WARN_ON_ONCE_NONRT is defined.
That being said I think we can just kill these asserts. If we have irqs
disabled spin_unlock_irq a few lines below should already warn.
Powered by blists - more mailing lists