lkml.org 
[lkml]   [2004]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ncpfs problems
> > > > unlink("kdeinit_maggie_2")              = -1 EBUSY (Device or resource busy)

> ncp_unlink closes file on server if there is no read or write
> operation in progress - see ncp_make_open, ncp_inode_close and
> ncp_make_closed: ncp_make_open opens file on server, ncp_inode_close
> marks file as being "closable" and ncp_make_closed closes file unless
> someone is in ncp_make_open - ncp_inode_close region.
>
> Cannot be kdeinit_maggie_2 opened by someone else?

Not another machine. This server currently allows only one NCP connection.
I have no idea which KDE processes that are opening this file, though.


> BTW, ncpfs is "single threaded" because protocol itself is single
> threaded - you can have only one outstanding request. Even with TCP
> transport which could allow more than one outstanding request, leaving
> synchronization on TCP level, if you send data to server while
> it processes another request some server versions return back 9999,
> server busy, instead of leaving received data in the queue until
> previous request is satisfied :-(

I guess it would be possible to use multiple TCP/NCP connections, but this
might be a bit overkill.


> Actually with 2.6.x fs/ncpfs/sock.c changing code to not call
> ncp_abort_connection() when something goes wrong should not be that
> hard. Only problem is that ncp_request_reply structure is allocated
> on caller stack, and so you must kill receiver (ncpdgram_rcv_proc/
> ncptcp_rcv_proc) before you release this structure.
>
> But main question is whether it is really needed... It works this way
> since day #1 (old kernels actually used SIGKILL|SIGSTOP, making
> debugging of processes using ncpfs filesystem almost impossible, yet
> nobody complained).

I can only speak for myself, but I do believe that this is a big problem
for us and our customers. I've filed a bug in the Bugzilla: Bug 3328.

--
Peter Åstrand Chief Developer
Cendio www.thinlinc.com
Teknikringen 3 www.cendio.se
583 30 Linköping Phone: +46-13-21 46 00


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.032 / U:0.844 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site