I partly agree to the wishlist opinion, for the part where I ask for a loading option, however, imho cifs has a bug where it ignores the sysctl setting.
Met vriendelijke groet,
Alexander Swen
From: "Ben Hutchings" <ben@decadent.org.uk>
To: "Alexander Swen" <alex@swen.nu>
Cc: 644135@bugs.debian.org
Sent: Friday, 7 October, 2011 7:03:59 AM
Subject: Bug#644135: cifs ignores sysct setting
On Mon, 2011-10-03 at 09:46 +0200, Alexander Swen wrote:
> Package: linux-mage
> Version: 2.6.32-5-amd64
>
> cifs.ko module (which is included in the kernel pkg as far as i know)
> cifs driver version 1.61
>
> when cifs module loads oplock is enabled by default.
> so I can do
> echo 0 >/proc/fs/cifs/OplockEnabled
> but that won't persist through a driver reload. so we tried adding
> this to /etc/sysctl.conf:
> fs.cifs.OplockEnabled = 0
[...]
> So, when I read the modinfo of cifs, there are a few module options,
> but no oplock option.
> I would like to add something like:
> options cifs oplocksenabled=0
> to /etc/modprobe.d/aliases.conf
>
> Is it feasible to add that param as an option?
[...]
You should ask the upstream developers (Steve French <sfrench@samba.org>
and linux-cifs@vger.kernel.org) for this feature.
Ben.
--
Ben Hutchings
For every action, there is an equal and opposite criticism. - Harrison