[Samba] 2.2.8a with kernel-2.4.22 has kernel oplock problems (NOT Failed to setup RT_SIGNAL_LEASE handler)

Urs Rau urs.rau at uk.om.org
Fri Mar 19 22:17:58 GMT 2004

I have a samba problem on a redhat 9 box that appears to be clearly linked to a new kernel 
2.4.22nptl when using "kernel oplocks = yes".

I am trying to install a printer driver on a win98se box that tries loading the driver files from a 
share on the 2.2.8a server. The installation fails as win98se cannot read all the files as it would 
like to.

I have two things I can do to avoid the problem.
1. if I set "kernel oplocks = no"
2. if I go back to the former kernel 2.4.20-19.9 without nptl
then the operation does not fail.

At first I thought it was just the annoying "Failed to setup RT_SIGNAL_LEASE handler" bug, but then 
I patched this as follows:
--- samba-2.2.7a/source/smbd/oplock_linux.c.orig	2003-06-05 14:40:49.000000000 -0400
+++ samba-2.2.7a/source/smbd/oplock_linux.c	2003-06-06 13:34:29.000000000 -0400
@@ -40,7 +40,7 @@

-#define RT_SIGNAL_LEASE 33

  #ifndef F_SETSIG
--- samba-2.2.7a/source/smbd/notify_kernel.c.orig	2003-06-06 13:33:56.000000000 -0400
+++ samba-2.2.7a/source/smbd/notify_kernel.c	2003-06-06 13:37:44.000000000 -0400
@@ -39,7 +39,7 @@

-#define RT_SIGNAL_NOTIFY 34

  #ifndef F_SETSIG

That did get rid of the "Failed to setup RT_SIGNAL_LEASE handler" messages in the log for both 
kernels 2.4.20 + 2.4.22 but I still can't install the printer driver files from the samba share when 
"kernel oplocks = yes".

I can't get to the bottom of this. I have a debug level 10 log file for this, would anybody be 
willing to look into it and tell me what I need to change?

Many thanks in advance.

Urs Rau
Head of IT
OM UK Headquarters

More information about the samba mailing list