Bug 16204

Summary: 2.6.35-rc3 regression linked to 597a264b1a9c7e36d1728f677c66c5c1f7e3b837
Product: Networking Reporter: Michael S. Tsirkin (m.s.tsirkin)
Component: OtherAssignee: Arnaldo Carvalho de Melo (acme)
Status: CLOSED CODE_FIX    
Severity: normal CC: maciej.rutecki, rjw
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.35-rc3 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 16055    
Attachments: .config of the kernel in question
bisect log
script to bring up tap interface
script to run qemu

Description Michael S. Tsirkin 2010-06-14 12:27:12 UTC 
I am using qemu with both tap and slirp (userspace) networking.
This works fine under 2.6.35-rc2 but breaks under 2.6.35-rc3:
ssh over slirp stops working sometimes right away
and sometimes after a bit of use.

Git bisect gave me this commit: 597a264b1a9c7e36d1728f677c66c5c1f7e3b837.

Reverting 597a264b1a9c7e36d1728f677c66c5c1f7e3b837 fixes the issue
for me.
Comment 1 Michael S. Tsirkin 2010-06-14 12:29:01 UTC 
Created attachment 26762 [details]
.config of the kernel in question
Comment 2 Michael S. Tsirkin 2010-06-14 12:34:18 UTC 
Created attachment 26763 [details]
bisect log
Comment 3 Michael S. Tsirkin 2010-06-14 13:15:14 UTC 
Created attachment 26764 [details]
script to bring up tap interface
Comment 4 Michael S. Tsirkin 2010-06-14 13:15:47 UTC 
Created attachment 26765 [details]
script to run qemu
Comment 5 Rafael J. Wysocki 2010-06-14 13:59:11 UTC 
Caused by:

commit 597a264b1a9c7e36d1728f677c66c5c1f7e3b837
Author: John Fastabend <john.r.fastabend@intel.com>
Date:   Thu Jun 3 09:30:11 2010 +0000

    net: deliver skbs on inactive slaves to exact matches

    Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>

First-Bad-Commit : 597a264b1a9c7e36d1728f677c66c5c1f7e3b837
Comment 6 Rafael J. Wysocki 2010-06-14 14:01:29 UTC 
A couple of notes.  First, the title of your report is meaningless (at least,
please say _what_ regression).  Second, providing a commit hash alone is not
really helpful.  Finally, this probably is a duplicate.
Comment 7 Michael S. Tsirkin 2010-06-14 14:14:16 UTC 
fixed by commit
e897082fe7a5b591dc4dd5599ac39081a7c8e482