1. 13 8月, 2008 1 次提交
  2. 30 7月, 2008 1 次提交
  3. 20 7月, 2008 1 次提交
  4. 15 7月, 2008 1 次提交
  5. 09 7月, 2008 1 次提交
    • J
      net/wireless/nl80211.c: fix endless Netlink callback loop. · b4637271
      Julius Volz 提交于
      Although I only tested similar code (I don't use any of this wireless
      code), the state maintainance between Netlink dump callback invocations
      seems wrong here and should lead to an endless loop. There are also other
      examples in the same file which might have the same problem. Perhaps someone
      can actually test this (or refute my logic).
      
      Take the simple example with only one element in the list (which should fit
      into the message):
      
      1. invocation:
        Start:
          idx = 0, start = 0
        Loop:
          condition (++idx < start) => (1 < 0) => false
          => no continue, fill one entry, exit loop, return skb->len > 0
      
      2. invocation:
        Start:
          idx = 0, start = 1
        Loop:
          condition (++idx < start) => (1 < 1) => false
          => no continue, fill the same entry again, exit loop, return skb->len > 0
      
      3. invocation:
        Same as 2. invocation, endless invocation of callback.
      
      Also, iterations where the filling of an element fails should not be counted as
      completed, so idx should not be incremented in this case.
      Signed-off-by: NJulius Volz <juliusv@google.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b4637271
  6. 25 6月, 2008 1 次提交
  7. 17 6月, 2008 10 次提交
  8. 15 6月, 2008 1 次提交
  9. 04 6月, 2008 1 次提交
  10. 15 5月, 2008 2 次提交
  11. 09 4月, 2008 1 次提交
  12. 08 4月, 2008 1 次提交
  13. 28 3月, 2008 1 次提交
  14. 26 3月, 2008 2 次提交
  15. 07 3月, 2008 1 次提交
  16. 01 3月, 2008 6 次提交
  17. 29 1月, 2008 8 次提交