[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56B1C03D.70203@lightnvm.io>
Date: Wed, 3 Feb 2016 09:54:21 +0100
From: Matias Bjørling <mb@...htnvm.io>
To: Javier González <jg@...htnvm.io>
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
Javier González <javier@...xlabs.com>
Subject: Re: [PATCH 1/2] lightnvm: warn if irqs are disabled in lock laddr
On 02/01/2016 11:34 AM, Javier González wrote:
> Add a warning if irqs are disabled when locking a new address in rrpc.
> The typical path to a new request does not disable irqs, but this is not
> guaranteed in the future.
>
> Signed-off-by: Javier González <javier@...xlabs.com>
> ---
> drivers/lightnvm/rrpc.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/lightnvm/rrpc.h b/drivers/lightnvm/rrpc.h
> index dfca5c4..c27283a 100644
> --- a/drivers/lightnvm/rrpc.h
> +++ b/drivers/lightnvm/rrpc.h
> @@ -184,6 +184,8 @@ static int __rrpc_lock_laddr(struct rrpc *rrpc, sector_t laddr,
> sector_t laddr_end = laddr + pages - 1;
> struct rrpc_inflight_rq *rtmp;
>
> + WARN_ON(irqs_disabled());
> +
> spin_lock_irq(&rrpc->inflights.lock);
> list_for_each_entry(rtmp, &rrpc->inflights.reqs, list) {
> if (unlikely(request_intersects(rtmp, laddr, laddr_end))) {
>
Thanks, applied for next -rc.
Powered by blists - more mailing lists