linux-kernel - Re: [PATCH] gpio/langwell: re-read the IRQ status register after each iteration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 11 May 2012 13:57:42 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Julia Lawall <julia.lawall@...6.fr>
Cc:	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	linux-kernel@...r.kernel.org, grant.likely@...retlab.ca,
	linus.walleij@...ricsson.com
Subject: Re: [PATCH] gpio/langwell: re-read the IRQ status register after each iteration

On Thu, May 10, 2012 at 10:34 PM, Julia Lawall <julia.lawall@...6.fr> wrote:

> I tried the following:
>
> @@
> expression pending,gedr,e1;
> statement S;
> @@
>
> *pending = readl(gedr);
> ... when != pending = e1
> while (pending) S
>
> That is, a readl call followed by a while loop with no reassignment of
> pending.
>
> Perhaps the following are suspicious:
>
> arch/arm/mach-msm/dma.c, function msm_datamover_irq_handler
> drivers/gpio/gpio-msm-v1.c, function msm_gpio_irq_handler
>
> But I am not completely sure to understand what is wanted (or not wanted).

No problem, I will look at them.
Thanks Julia!

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/