Re: [KJ][PATCH 03/04]use set_current_state in fs

On 11:39 Sat 14 Apr     , Eric Dumazet wrote:
> Milind Arun Choudhary a écrit :
> >use set_current_state(TASK_*) instead of current->state = TASK_*, in fs/nfs
> Probably a dumb question, so please forgive me.
no.
you have a valid point

My bad :(
I should probably be enjoying my weekend outdoors..
breath some fresh air...
rather than sending such dumb patches..

ummmmmmmm
booting into  windows might help :)

> Why are you  forcing a memory barrier here, (and also on your other 
> patches).
> Is'nt a  __set_current_state(TASK_RUNNING); appropriate ?
it is..

would resend later

Njo!!!
-- 
Milind Arun Choudhary
-
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:
  • [KJ][PATCH 03/04]use set_current_state in fs
    • From: Milind Arun Choudhary <[email protected]>
  • Re: [KJ][PATCH 03/04]use set_current_state in fs
    • From: Eric Dumazet <[email protected]>

• Prev by Date: [RFC] [Patch 4/4] timer_stats slimmed down: using statistics infrastucture
• Next by Date: Re: MOXA: mxser_new lockup
• Previous by thread: Re: [KJ][PATCH 03/04]use set_current_state in fs
• Next by thread: [KJ][PATCH 04/04]use set_current_state in fs
• 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]