Okay this case is getting weirder. I installed 3.7.0-2.8 from the link and I also installed the 3.5.7 mainline build and both seemed fine. However, I was eventually able to boot into a 3.5.0-18 session that could actually connect without throwing samba panics. By chance I was able to discover that restarting smbd will (as far as I can tell) guarantee hitting the samba panic on the next connection for affected kernels. So if I boot into 3.5.0-18 and there is no panic right away I will hit one if I restart smbd (presumably if I wait long enough then the panics might show up anyway without needing a restart as is alluded to in the upstream bug report). Testing on 3.2.0 confirmed that it was immune to this issue because restarting samba did not cause all subsequent connections to cause a panic.
Testing all the kernels again using this new method it seems that kernels 3.3 and 3.4 are fine, but starting with 3.5.0rc4 I can trigger the bug so perhaps my 3.7 report from yesterday wasn't a mistake on my part after all. I tried the restart smbd trick in a 12.10 install and I'm still not able to cause a panic there. I can go try testing the earlier 3.5rcs but I think at this point it might be better to build newer versions of samba and see if they fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075670 Title: samba panics with sys_setgroups failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1075670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
