Re: [PATCH 1/2] irq_flags_t: intro and core annotations

Hi,

On Sun, 28 Oct 2007, Alexey Dobriyan wrote:

> > If it's just about the type checking, something like below should pretty 
> > much do the same.
> 
> It won't catch, the following if both variables are unsigned long:
> 
> 	spin_lock_irqsave(&lock, flags);
> 		[stuff]
> 	spin_unlock_irqrestore(&lock, foo->flags);
> 
> It won't catch "static unsigned long flags;". With sparse, we can
> eventually mark type as "on-stack only".

It should be on the stack, but we have cases where a pointer to it is used 
(e.g. lock_timer_base). How do you want to deal with this?

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/2] irq_flags_t: intro and core annotations
    • From: Alexey Dobriyan <[email protected]>
  • Re: [PATCH 1/2] irq_flags_t: intro and core annotations
    • From: Roman Zippel <[email protected]>
  • Re: [PATCH 1/2] irq_flags_t: intro and core annotations
    • From: Alexey Dobriyan <[email protected]>

• Prev by Date: Re: fixing up DRM device model usage
• Next by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
• Previous by thread: Re: [PATCH 1/2] irq_flags_t: intro and core annotations
• Next by thread: [PATCH] Fix sched_domain sysctl registration again
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]