From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: David Jander <david.jander@protonic.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ncpfs, kernel 2.4.18
Date: Fri, 4 Apr 2003 13:45:41 +0200 [thread overview]
Message-ID: <64319A7E14@vcnet.vc.cvut.cz> (raw)
On 4 Apr 03 at 13:24, David Jander wrote:
> This fixes a bug with Novell Netware Servers (in my case 3.12) sending error
> messages (and annoying beeps) to the console each time a linux client
> accesses de root directory of a volume. Please comment !
> Please send replies with CC to me, since I am not subscribed to lkml.
What they say? It is completely legal to use NULL path in ncp_obtain_info,
and in reality ncp_obtain_mtime() in fs/ncpfs/dir.c uses NULL path
explicitly (and it also checks for 'ncp_is_server_root(inode)', at least
in 2.5.66 and 2.4.19). See ncp_add_handle_path, it contains code which
converts NULL path to no path at all.
Do not you just have loaded some misguided antivirus software on your server?
ncpfs uses inode based addressing scheme, where files are accessed by their
numbers instead of name. Only thing which accesses files by name are
validating functions, for converting name to number, and unlink (because of
4.x servers crash when unlink by inode is invoked on NFS namespace).
Petr Vandrovec
next reply other threads:[~2003-04-04 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 11:45 Petr Vandrovec [this message]
2003-04-04 12:33 ` [PATCH] ncpfs, kernel 2.4.18 David Jander
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 13:23 Petr Vandrovec
2003-04-04 11:24 David Jander
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=64319A7E14@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=david.jander@protonic.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox