debian/changelog  |    7 +++++++
 net/core/skbuff.c |   13 ++++++++++---
 2 files changed, 17 insertions(+), 3 deletions(-)

New commits:
commit d74fa1db2f8069c96d1f0450762e81315a979504
Author: Stephen Hemminger <[email protected]>
Date:   Wed Jun 17 18:24:25 2009 -0700

    2.6.29-5+vyatta+6+jenner2

commit c4366e44ac184ebb6597476eb975de7658446465
Author: Stephen Hemminger <[email protected]>
Date:   Wed Jun 17 15:17:34 2009 -0700

    skbuff: don't corrupt mac_header on skb expansion
    
    The skb mac_header field is sometimes NULL (or ~0u) as a sentinel
    value. The places where skb is expanded add an offset which would
    change this flag into an invalid pointer (or offset).
    
    Signed-off-by: Stephen Hemminger <[email protected]>

commit f5f82a3471410be44802fa9180a819cf915e6812
Author: Stephen Hemminger <[email protected]>
Date:   Wed Jun 17 08:23:27 2009 -0700

    skbuff: skb_mac_header_was_set is always true on >32 bit
    
    Looking at the crash in log_martians(), one suspect is that the check for
    mac header being set is not correct.  The value of mac_header defaults to
    0 on allocation, therefore skb_mac_header_was_set will always be true on
    platforms using NET_SKBUFF_USES_OFFSET.
    
    Arnaldo, is this correct?
    
    Signed-off-by: Stephen Hemminger <[email protected]>

http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=d74fa1db2f8069c96d1f0450762e81315a979504
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=c4366e44ac184ebb6597476eb975de7658446465
http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=f5f82a3471410be44802fa9180a819cf915e6812
_______________________________________________
svn mailing list
[email protected]
http://mailman.vyatta.com/mailman/listinfo/svn

Reply via email to