LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Grant Coady <grant_lkml@dodo.com.au>
To: Willy Tarreau <w@1wt.eu>
Cc: Santiago Garcia Mantinan <manty@debian.org>,
Grant Coady <gcoady.lk@gmail.com>, dann frazier <dannf@dannf.org>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: problems with latest smbfs changes on 2.4.34 and security backports
Date: Mon, 22 Jan 2007 21:46:14 +1100 [thread overview]
Message-ID: <dv39r2pr5piq27lbou66jg963tqg3f3ahj@4ax.com> (raw)
In-Reply-To: <20070122091816.GA5144@1wt.eu>
On Mon, 22 Jan 2007 10:18:16 +0100, Willy Tarreau <w@1wt.eu> wrote:
>Grant, just to be sure, are you really certain that you tried the fixed kernel ?
>It is possible that you booted a wrong kernel during one of your tests. I'm
>intrigued by the fact that it changed nothing for you and that it fixed the
>problem for Santiago.
Closest I get to Santiago's results are with the 2.4.33.7 plus the patch,
with 'use default NLS' option turned on, as well as the unix extensions.
2.4.34 was a no go for me. Changing the default NLS made no difference,
now trying with unix extensions turned on. . . Yeah, that works, apart
from the test file gaining execute bits, compared to operation under
2.4.33.3, this is 2.4.34 + patch + default NLS and unix extensions:
grant@sempro:/home/other$ cat dirlink/filelink
this is a test
grant@sempro:/home/other$ echo "this is a test" > testfile
grant@sempro:/home/other$ ls -l
total 4096
drwxr-xr-x 1 grant wheel 0 2007-01-21 11:44 dir/
lrwxr-xr-x 1 grant wheel 3 2007-01-21 11:43 dirlink -> dir/
-rwxr-xr-x 1 grant wheel 15 2007-01-21 11:43 file*
lrwxr-xr-x 1 grant wheel 4 2007-01-21 11:44 filelink -> file*
drwxr-xr-x 1 grant wheel 0 2007-01-22 10:45 test/
-rwxr-xr-x 1 grant wheel 15 2007-01-22 21:31 testfile*
lrwxr-xr-x 1 grant wheel 4 2007-01-22 21:29 testlink -> test/
grant@sempro:/home/other$ ln -s testfile testfilelink
grant@sempro:/home/other$ cat testfilelink
this is a test
The fix depends on the smbfs configuration? Is this the requirement?
I ask as the other mode of operation (unix extensions turned off): do
not display symlinks, prevent creation of symlinks, seems to be logically
self-consistent, as well as matching what I see from a 'doze box.
Grant.
next prev parent reply other threads:[~2007-01-22 10:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 10:00 problems with latest smbfs changes on 2.4.34 and security backports Santiago Garcia Mantinan
2007-01-17 21:55 ` Willy Tarreau
2007-01-18 0:09 ` Grant Coady
2007-01-18 4:21 ` Willy Tarreau
2007-01-18 5:59 ` Grant Coady
2007-01-18 22:51 ` dann frazier
2007-01-19 1:00 ` dann frazier
2007-01-19 5:15 ` Willy Tarreau
2007-01-20 1:05 ` dann frazier
2007-01-20 6:18 ` Willy Tarreau
2007-01-21 22:52 ` Grant Coady
2007-01-21 23:03 ` Willy Tarreau
2007-01-21 23:50 ` Grant Coady
2007-01-22 18:19 ` dann frazier
2007-01-23 5:42 ` Willy Tarreau
2007-01-23 21:12 ` dann frazier
2007-01-23 22:00 ` Willy Tarreau
2007-01-23 23:46 ` Grant Coady
2007-01-24 0:11 ` dann frazier
2007-01-22 8:54 ` Santiago Garcia Mantinan
2007-01-22 9:18 ` Willy Tarreau
2007-01-22 9:36 ` Santiago Garcia Mantinan
2007-01-22 10:49 ` Grant Coady
2007-01-22 10:46 ` Grant Coady [this message]
2007-01-23 20:19 ` dann frazier
2007-01-23 21:04 ` Grant Coady
2007-01-23 21:35 ` dann frazier
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=dv39r2pr5piq27lbou66jg963tqg3f3ahj@4ax.com \
--to=grant_lkml@dodo.com.au \
--cc=dannf@dannf.org \
--cc=debian-kernel@lists.debian.org \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manty@debian.org \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).