From: Nigel Kukard <nkukard@lbsd.net>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMBFS crash
Date: Tue, 8 Jun 2004 20:05:09 +0200 [thread overview]
Message-ID: <20040608180508.GI14247@lbsd.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0406081259570.1838@montezuma.fsmlabs.com>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Thanks man, will test it out
-Nigel
On Tue, Jun 08, 2004 at 01:06:23PM -0400, Zwane Mwaikambo wrote:
> On Tue, 8 Jun 2004, Nigel Kukard wrote:
>
> > I get the following error trying to access a mounted smb filesystem.
> > 100% reproducable on my sytem.
> >
> > Please let me know if you require anymore info.
>
> A known issue, there is also a bugzilla entry at the following URL with a
> temporary fix (needs a bit of work to satisfy the maintainer, which i'll
> get round to one of these evenings).
>
> http://bugme.osdl.org/show_bug.cgi?id=1671
>
> Feel free to add yourself to the Cc list.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-06-08 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 12:36 SMBFS crash Nigel Kukard
2004-06-08 17:06 ` Zwane Mwaikambo
2004-06-08 18:05 ` Nigel Kukard [this message]
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=20040608180508.GI14247@lbsd.net \
--to=nkukard@lbsd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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