* Maneesh Soni <[email protected]> wrote: > > I'm already playing around with this. You might want this patch instead. > > I noticed that if sysfs_make_dirent fails to allocate the sd, then a > > null will be passed to sysfs_put. > Agreed. This makes more sense. ok, i've applied Steven's patch. Ingo - 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:
- What protection does sysfs_readdir have with SMP/Preemption?
- From: Steven Rostedt <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Greg KH <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Maneesh Soni <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Steven Rostedt <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Maneesh Soni <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Steven Rostedt <[email protected]>
- Re: What protection does sysfs_readdir have with SMP/Preemption?
- From: Maneesh Soni <[email protected]>
- What protection does sysfs_readdir have with SMP/Preemption?
- Prev by Date: Re: [patch] SMP alternatives
- Next by Date: Re: [OOPS] sysfs_hash_and_remove (was Re: What protection ....)
- Previous by thread: Re: What protection does sysfs_readdir have with SMP/Preemption?
- Next by thread: [2.4.31 + aic79xx] SCSI error: Infinite interrupt loop, INTSTAT = 0
- Index(es):
 |