Updated Samba Client

[Paul Smedley]

Samba 4.19.6 (and above) and 4.20.x are giving SIGSEGVs,  trying to work out what broke....

Edit: 4.19.6+  are giving SIGSEGV,  4.20.x  is just broken (talking smbd here, not the client)

[David McKenna]

 I wonder why... were there a lot of changes from 4.19.4?

Regards,

[Paul Smedley]

I wonder why... were there a lot of changes from 4.19.4?

I'l have to go through them... As I recall,  4.19.5  was ok...

[David McKenna]

 Went back to 4.19.4 because WINBINDD wouldn't start with 4.19.5 (but you said it was because of attempts to fix the RPC issue), but smbd did run and work at least...

Regards,

[Paul Smedley]

Reverting my 4.19.x branch back to 4.19.5  and will rebuild it and confirm it works  - might help narrow down what broke...

[Paul Smedley]

Confirming that 4.19.5 smbd runs.... switching to 4.19.6 now to remind myself how that one failed..... should narrow down the amount of changes to review  to determine what broke.

[Paul Smedley]

well.... after rebuilding 4.19.6 and 4.19.7 -  both seem to be working after light testing...

Full package: https://smedley.id.au/tmp/samba-4.19.7-os2-20240626.zip
Client DLL: https://smedley.id.au/tmp/smbcl419-4.19.7-20240626.zip

net rpc issue is still unresolved (pipes on OS/2 are a PITA)

Now to work out why the server from 4.20 is aborting connections....

[David McKenna]

 Thanks Paul! Both seem to be working as well as 4.19.4 here so far. No NET RPC as you mention. I'll give them a more thorough workout after work and let you know if any issue arises...

Regards,

[Paul Smedley]

Thanks for testing Dave... the whole named pipe issue is a complete PITA....

[Paul Smedley]

No specific fixes, other than tweaks to fix issues with GCC 14.1.0... All code rebuilt with GCC 14.1 as part of compiler validation...

https://smedley.id.au/tmp/samba-4.19.7-os2-20240712.zip

[David McKenna]

Hey Paul,

  Something seriously wrong with this one - soon as I start the server the computer freezes solid. Have to hit the reset switch (or turn it off). No POPUPLOG, no exceptq trap reports or anything left behind as a clue. Had to boot to a AOS DVD and delete from there, then re-install your last drop of 4.19.7 (which works well)...

Regards,

[Paul Smedley]

Interesting, smbd starts/runs fine here and can accept connections.....

[Steven Levine]

David,

Can I assume that CAD failed to pop up CADH?

If you can get CADH to pop up, you can usually capture a process dump, even if you cannot kill the app that is hung.

If CADH will not pop up, you could try to capture a system dump.  This would likely tell us where smbd is going astray.

Steven

[David McKenna]

 Steven,

  Couldn't get to CADH - no mouse or keyboard input was working. I have some more time today, so I'll try again and see if I can get it to work. If not, I'll try to get a dump.

Regards,

[Steven Levine]

David,

Most of the time, Ctrl-Alt-F10-F10 will bring up the system dump prompts, even if the keyboard is not responding to normal keystrokes.  Whether or not you will be able to capture a system dump, depends on your boot environment, much more than it used to.

Depending on what starting smbd breaks, you still might be able to capture a process dump.

 - open a command line session where you will start smbd
 - open a 4os2 session where you will manage the process dump facility
 - configure the process dump facility with something like
      pdumpctl n f v smbd
     delay 30 & pdumpctl f smbd
 - switch to the smbd command line session and start smbd

If the system is sufficiently alive after smbd starts, pdumpctl will force a process dump after 30 seconds