2.6.14 kernels and above copy_to_user stupidity with IRQ disabled check

["Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>]

Is there a good reason someone set a disabled_irq() check on 2.6.14 and 
above for copy_to_user to barf out
tons of bogus stack dump messages if the function is called from within 
a spinlock:

i.e.

spin_lock_irqsave(&regen_lock, regen_flags);
   v = regen_head;
   while (v)
   {
      if (i >= count)
         return -EFAULT;
                                                                               

      err = copy_to_user(&s[i++], v, sizeof(VIRTUAL_SETUP));
      if (err)
         return err;
                                                                               

      v = v->next;
   }
   spin_unlock_irqrestore(&regen_lock, regen_flags);

is now busted and worked in kernels up to this point.  The error message 
is annoying but non-fatal.

Jeff


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