Your message dated Wed, 10 Jul 2013 20:09:13 +0200
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #644135,
regarding cifs should have module parameter or sysctl for OplockEnabled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
644135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644135
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
however:
root@nl14s0008-vm1:~# echo 0 >/proc/fs/cifs/OplockEnabled
root@nl14s0008-vm1:~# cat /proc/fs/cifs/OplockEnabled
0
root@nl14s0008-vm1:~# modprobe -r cifs
root@nl14s0008-vm1:~# tail -1 /etc/sysctl.conf
fs.cifs.OplockEnabled = 0
root@nl14s0008-vm1:~# lsmod|grep cifs
root@nl14s0008-vm1:~# modprobe cifs
root@nl14s0008-vm1:~# !l
lsmod |grep cifs
cifs 262528 0
nls_base 6377 3 cifs,nls_utf8,usbcore
root@nl14s0008-vm1:~# !cat
cat /proc/fs/cifs/OplockEnabled
1
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?
I use the cifs 1.61 module on 2.6.32-5-amd64 kernel on Debian 6.0 (Debian
2.6.32-35squeeze2)
Met vriendelijke groet,
Alexander Swen
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to [email protected] with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
