mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Saout <christophe@saout.de>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Brice Goglin <Brice.Goglin@ens-lyon.fr>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7 Samba OOPS (in smb_readdir)
Date: Fri, 18 Jun 2004 21:22:12 +0200	[thread overview]
Message-ID: <1087586532.9085.1.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <1087585251.13235.3.camel@leto.cs.pocnet.net>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Am Fr, den 18.06.2004 um 21:00 Uhr +0200 schrieb Christophe Saout:

> > 	It's a known issue currently being tracked with the bugzilla entry
> > at http://bugzilla.kernel.org/show_bug.cgi?id=1671
> 
> Hey, nice.
> 
> I've got a nearly 100% reproducability of the problem here (FAM +
> nautilus + hal.hotplug or something like that, I'm always getting this
> Oops in nautilus trying to do something with its trash folder when I'm
> mounting a remote volume). I'll try this patch and tell you if it's
> working (for me).

Well, it's not. :(

The oops is gone but the processes are still hanging. I'm posting the
SysRq-T trace on bugzilla. Hope it helps. If you need some help
debugging the problem, please tell me if I can do something.


[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-18 19:48 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16  5:56 Linux 2.6.7 Linus Torvalds
2004-06-16  6:58 ` Kalin KOZHUHAROV
2004-06-16 14:56   ` Jesper Juhl
2004-06-16  7:10 ` Jan De Luyck
2004-06-16  8:07 ` JFS compilation fix [was Re: Linux 2.6.7] Tomas Szepe
2004-06-16 12:55   ` Dave Kleikamp
2004-06-16 12:59     ` Dave Kleikamp
2004-06-16 13:05     ` Tomas Szepe
2004-06-16  9:58 ` Linux 2.6.7 (stty rows 50 columns 140 reports : No such device or address) Zilvinas Valinskas
2004-06-16 12:55   ` Jeff Garzik
2004-06-16 13:56     ` Benjamin Herrenschmidt
2004-06-16 16:38       ` jsimmons
2004-06-16 14:17     ` Zilvinas Valinskas
2004-06-16 16:37       ` jsimmons
2004-06-16 21:17         ` Egmont Koblinger
2004-06-16 21:45           ` jsimmons
2004-06-16 11:13 ` Linux 2.6.7 Tomas Szepe
2004-06-16 12:18   ` viro
2004-06-17  6:56     ` Tomas Szepe
2004-06-16 13:27 ` Linux 2.6.7 - problem with old gcc Eyal Lebedinsky
2004-06-16 16:09 ` Linux 2.6.7 (compile stats) John Cherry
2004-06-16 16:31 ` Linux 2.6.7 Dominik Karall
2004-06-16 18:53   ` Jeff Garzik
2004-06-16 17:42 ` Linux 2.6.7 - ACPI still broken Thomas Zehetbauer
2004-06-17  4:15   ` Kevin P. Fleming
2004-06-17 15:22 ` Linux 2.6.7 Sean Neakums
2004-06-18  4:36   ` Andrew Morton
2004-06-18 16:37 ` 2.6.7 Samba OOPS (in smb_readdir) Brice Goglin
2004-06-18 16:41   ` Brice Goglin
2004-06-18 17:11     ` Zwane Mwaikambo
2004-06-18 19:00       ` Christophe Saout
2004-06-18 19:22         ` Christophe Saout [this message]
2004-06-18 19:52           ` Zwane Mwaikambo
2004-06-19 20:35           ` Zwane Mwaikambo
2004-06-19 20:49             ` Zwane Mwaikambo
2004-06-19 20:52               ` Christophe Saout
2004-06-20  0:27               ` Zwane Mwaikambo
2004-06-20  0:28                 ` Christophe Saout
2004-06-20  0:36                   ` Zwane Mwaikambo
2004-06-20  0:40                     ` Christophe Saout

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=1087586532.9085.1.camel@leto.cs.pocnet.net \
    --to=christophe@saout.de \
    --cc=Brice.Goglin@ens-lyon.fr \
    --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

all inboxes | Powered by JetHome®