On Sat, Oct 28, 2006 at 03:23:40PM +0200, Eric Dumazet ([email protected]) wrote:
> >diff --git a/kernel/kevent/kevent_user.c b/kernel/kevent/kevent_user.c
> >index 711a8a8..ecee668 100644
> >--- a/kernel/kevent/kevent_user.c
> >+++ b/kernel/kevent/kevent_user.c
> >@@ -235,6 +235,36 @@ static void kevent_free_rcu(struct rcu_h
> > }
> >
> > /*
> >+ * Must be called under u->ready_lock.
> >+ * This function removes kevent from ready queue and
> >+ * tries to add new kevent into ring buffer.
> >+ */
> >+static void kevent_remove_ready(struct kevent *k)
> >+{
> >+ struct kevent_user *u = k->user;
> >+
> >+ list_del(&k->ready_entry);
>
> Arg... no
>
> You cannot call list_del() , then check overflow_kevent.
>
> I you call list_del on what happens to be the kevent pointed by
> overflow_kevent, you loose...
This function is always called from appropriate context, where it is
guaranteed that it is safe to call list_del:
1. when kevent is removed. It is called after check, that given kevent
is in the ready queue.
2. when dequeued from ready queue, which means that it can be removed
from that queue.
--
Evgeniy Polyakov
-
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/
[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]
