From: Steve French <smfltc@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: eyal@eyal.emu.id.au, linux-kernel@vger.kernel.org,
linux-cifs-client@lists.samba.org
Subject: Re: 2.6.10-rc2-mm4 - cifs.ko needs unknown symbol CIFSSMBSetPosixACL
Date: Wed, 01 Dec 2004 01:33:04 -0600 [thread overview]
Message-ID: <41AD73B0.8080004@us.ibm.com> (raw)
In-Reply-To: <20041130225303.7abb16b8.akpm@osdl.org>
Andrew Morton wrote:
>Steve French <smfltc@us.ibm.com> wrote:
>
>
>> The CIFS code has had major recent update (most importantly the
>> cifs_readdir rewrite which can be enabled in mm by "echo 1 >
>> /proc/fs/cifs/NewReaddirEnabled",
>>
>>
>
>Nobody will do that, so the new code won't get tested.
>
>In keeping with my evil plan to drive -mm users insane, could I ask that
>you send me a diff which will make the new readdir code default to "on"?
>
>
>
OK - done. Default is now to use cifs_readdir2 (new code) and to go
back to the old code -
"echo 1 > /proc/fs/cifs/ReenableOldCifsReaddirCode"
The update is in the cifs bk tree (bk://cifs.bkbits.net/linux-2.5cifs)
and this particular minor patch in diff -Nau form is:
http://cifs.bkbits.net:8080/linux-2.5cifs/gnupatch@41ad739b4xCWzpJKDse0JW4Ep5y3LQ
next prev parent reply other threads:[~2004-12-01 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 6:42 2.6.10-rc2-mm4 - cifs.ko needs unknown symbol CIFSSMBSetPosixACL Steve French
2004-12-01 6:53 ` Andrew Morton
2004-12-01 7:33 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-30 17:50 2.6.10-rc2-mm4 Andrew Morton
2004-11-30 23:07 ` 2.6.10-rc2-mm4 - cifs.ko needs unknown symbol CIFSSMBSetPosixACL Eyal Lebedinsky
2004-11-30 23:53 ` Andrew Morton
2004-12-01 8:43 ` Eyal Lebedinsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41AD73B0.8080004@us.ibm.com \
--to=smfltc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=eyal@eyal.emu.id.au \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.