Re: [PATCH 2/3] Don't change transfer speed while requests are in flight

> +	 * If we are in an interrupt, it should be safe to issue
> +	 * SETFEATURES manually, since there shouldn't be any requests in
> +	 * flight.

There may be error recovery going on from a timeout on another processor.
I don't see how your code protects against that (and the old code is
broken too)

-
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 2/3] Don't change transfer speed while requests are in flight
  - From: Suleiman Souhlal <[email protected]>

Prev by Date: x86_64: PTRACE_[GS]ET_THREAD_AREA should be accepted
Next by Date: Re: 2.6.20-git13 kernel BUG at /mnt/md0/devel/linux-git/kernel/time/tick-sched.c:168
Previous by thread: Re: [PATCH 2/3] Don't change transfer speed while requests are in flight
Next by thread: [PATCH] [MTD] CHIPS: oops in cfi_amdstd_sync
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]