Re: [RFC][PATCH 2/9] deadlock prevention core

I think the new atomic operation that will seemingly occur on every
device SKB free is unacceptable.

You also cannot modify netdev->flags in the lockless manner in which
you do, it must be done with the appropriate locking, such as holding
the RTNL semaphore.
-
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: [RFC][PATCH 2/9] deadlock prevention core
  - From: Daniel Phillips <[email protected]>

References:
- [RFC][PATCH 0/9] Network receive deadlock prevention for NBD
  - From: Peter Zijlstra <[email protected]>
- [RFC][PATCH 2/9] deadlock prevention core
  - From: Peter Zijlstra <[email protected]>

Prev by Date: Re: [PATCH] CONFIG_RELOCATABLE modpost fix
Next by Date: Re: [Patch] restore the RCU callback to defer put_task_struct() Re: Problems with 2.6.17-rt8
Previous by thread: Re: [RFC][PATCH 2/9] deadlock prevention core
Next by thread: Re: [RFC][PATCH 2/9] deadlock prevention core
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]