Bug 8358 - smbd exits with NT_STATUS_INTERNAL_ERROR in run_poll_events()
Summary: smbd exits with NT_STATUS_INTERNAL_ERROR in run_poll_events()
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.6.0rc3
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba QA Contact
Depends on:
Reported: 2011-08-08 17:04 UTC by Andreas Schneider
Modified: 2011-08-09 11:29 UTC (History)
1 user (show)

See Also:

Patch for 3.6 (1.25 KB, patch)
2011-08-09 08:47 UTC, Andreas Schneider
vl: review+
asn: review+

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Schneider 2011-08-08 17:04:42 UTC
smbd exits with NT_STATUS_INTERNAL_ERROR in run_poll_events(). We need to ignore fd events without EVENT_FD_READ or EVENT_FD_WRITE also in run_events_poll() too.

Patches for 3.6 and 3.5 are following.
Comment 1 Andreas Schneider 2011-08-08 17:23:15 UTC
I wasn't able to trigger this problem in production code. This only happens if smbd proxies a named pipe connection to an external daemon over a unix socket.

So this doesn't block the release but probably should be fixed in earlier versions. At least in 3.6 as you're able to enable the endpoint mapper daemon in 3.6.
Comment 2 Jeremy Allison 2011-08-08 20:44:53 UTC
Please add the patches asap. Not a blocker for release (IMHO).
Comment 3 Andreas Schneider 2011-08-08 20:55:30 UTC
I would like to, but I'm not able to check them in cause the Samba4 'make test' is failing.
Comment 4 Andreas Schneider 2011-08-09 08:47:06 UTC
Created attachment 6764 [details]
Patch for 3.6
Comment 5 Andreas Schneider 2011-08-09 08:52:31 UTC
Looks like this is not needed in 3.5. The events get removed from the list.
Comment 6 Andreas Schneider 2011-08-09 08:54:21 UTC
Comment on attachment 6764 [details]
Patch for 3.6

I've tested the patch and it fixes the problems I see with named pipe proxies here.
Comment 7 Karolin Seeger 2011-08-09 11:29:29 UTC
Pushed to v3-6-test.
Will be included in 3.6.0.
Closing out bug report.