From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: NCPFS and brittle connections
Date: Thu, 04 Jan 2007 09:26:50 -0800 [thread overview]
Message-ID: <459D38DA.4030803@vc.cvut.cz> (raw)
In-Reply-To: <459D1794.2060009@drzeus.cx>
Pierre Ossman wrote:
> Hi Petr,
>
> What is the status of this bug?
>
> http://bugzilla.kernel.org/show_bug.cgi?id=3328
>
> I do not see anything in the history of fs/ncpfs that seems to suggest that this, rather critical, issue has been resolved. Is anyone working on it?
Nobody is working on it (at least to my knowledge), and to me it is
feature - it always worked this way, like smbfs did back in the past -
if you send signal 9 to process using mount point, and there is some
transaction in progress, nobody can correctly finish that transaction
anymore. Fixing it would require non-trivial amount of code, and given
that NCP itself is more or less dead protocol I do not feel that it is
necessary.
If you want to fix it, feel free. Culprit is RQ_INPROGRESS handling in
ncp_abort_request - it just aborts whole connection so it does not have
to provide temporary buffers and special handling for reply - as buffers
currently specified as reply buffers are owned by caller, so after
aborting request you cannot use them anymore.
Petr Vandrovec
next prev parent reply other threads:[~2007-01-04 17:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 15:04 NCPFS and brittle connections Pierre Ossman
2007-01-04 17:26 ` Petr Vandrovec [this message]
2007-01-04 19:30 ` Pierre Ossman
2007-01-05 7:43 ` Petr Vandrovec
2007-01-24 15:27 ` Pierre Ossman
2007-01-24 17:49 ` Petr Vandrovec
2007-01-24 22:01 ` Pierre Ossman
2007-01-25 8:22 ` Petr Vandrovec
2007-01-25 10:20 ` Pierre Ossman
2007-02-01 8:39 ` Pierre Ossman
2007-02-04 6:00 ` Petr Vandrovec
2007-02-04 17:17 ` Pierre Ossman
2007-02-05 3:50 ` Petr Vandrovec
2007-02-19 10:37 ` Pierre Ossman
2007-02-20 2:47 ` Petr Vandrovec
2007-02-20 6:37 ` Pierre Ossman
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=459D38DA.4030803@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=drzeus-list@drzeus.cx \
--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.