Re: [PATCH resend] Fix a lock problem in generic phy code

Hans-J??rgen Koch <[email protected]> wrote:
>
> The following patch fixes it. Tested on an AT91SAM9263-EK board, kernel 2.6.23-rc4 and -rc3-mm1.

Could you please audit all instances of physdev->lock and add
_bh where necessary?  I can see that at least phys_stop also
needs the _bh.

We should also consider whether it makes sense to move the
timer into a work queue.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
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/

Follow-Ups:
- Re: [PATCH resend] Fix a lock problem in generic phy code
  - From: Hans-Jürgen Koch <[email protected]>

References:
- [PATCH resend] Fix a lock problem in generic phy code
  - From: Hans-Jürgen Koch <[email protected]>

Prev by Date: Toshiba A305 hda-intel (Was: Re: easy alsa patches for the stablekernel?)
Next by Date: Re: SATA problems
Previous by thread: [PATCH resend] Fix a lock problem in generic phy code
Next by thread: Re: [PATCH resend] Fix a lock problem in generic phy code
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]