winreg: QueryValue crashes on NULL pointer dereference (already fixed in master)
Created attachment 5738 [details] patch for 3.5 (the core server fix and also enable RPC-WINREG during make test)
Created attachment 5739 [details] fixed version of that patch (enabled wrong test)
The patches look fine.
The patchset contains three fixes (plus the enabling of WINREG-RPC). * there are actually two fixes of NULL handling (for in.name and for out.data) => ok for these * the "change notify call" patch does not seem to be related? Is it just to make smbtorture not fail? I don't quite understand it. * I guess we can enable the test again when it passes...
(In reply to comment #4) > The patchset contains three fixes (plus the enabling of WINREG-RPC). > > * there are actually two fixes of NULL handling > (for in.name and for out.data) > => ok for these good, thanks > * the "change notify call" patch does not seem to be related? > Is it just to make smbtorture not fail? yes. It was really sad that we didnt have RPC-WINREG running against s3 earlier which probably would have catched that. > I don't quite understand it. > * I guess we can enable the test again when it passes... yes, this what that patch is about. taking this as a +1 and reassigning to karolin for inclusion.
Pushed to v3-5-test. Closing out bug report. Thanks!
(In reply to comment #5) > (In reply to comment #4) > > The patchset contains three fixes (plus the enabling of WINREG-RPC). > > > > * there are actually two fixes of NULL handling > > (for in.name and for out.data) > > => ok for these > > good, thanks > > > * the "change notify call" patch does not seem to be related? > > Is it just to make smbtorture not fail? > > yes. It was really sad that we didnt have RPC-WINREG running against s3 earlier > which probably would have catched that. > > > I don't quite understand it. > > * I guess we can enable the test again when it passes... > > yes, this what that patch is about. > > taking this as a +1 and reassigning to karolin for inclusion. Yes, ok! :-)