From: Steven Cole <elenstev@mesatop.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67 kernel BUG at fs/buffer.c:2538
Date: 08 Apr 2003 15:16:14 -0600 [thread overview]
Message-ID: <1049836574.32480.1156.camel@spc9.esa.lanl.gov> (raw)
In-Reply-To: <1049815653.32665.1135.camel@spc9.esa.lanl.gov>
On Tue, 2003-04-08 at 09:27, Steven Cole wrote:
> This may be a case of:
>
> "It hurts when I do this:"
> "Then don't do that!"
>
> I started the latest security updated package of samba with
> kernel 2.5.67, but I had forgotten to set CONFIG_SMB_FS.
> The box became unresponsive, and then locked hard. Didn't respond
> to pings, etc. So I had to alt-sysrq-b. Now, samba is broken somehow,
> ERROR: Samba cannot create a SAM SID.
> so I can't presently retest with SMB_FS=y and 2.5.67 or with
> the vendor kernel (2.4.21-0.13mdk). Unfortunately I had not yet
> tested the new security updated packages for samba with the vendor kernel.
>
> However dumb it was to start samba without SMB_FS enabled,
> the box shouldn't die like this.
>
> I'm going to replace Bamboo with Shrike on that machine today,
> so I won't be able to reproduce this anytime soon. (I hope).
>
Replying to myself with an update. After reading the fs/Kconfig help
for SMB_FS I now realize that having that compiled in or not was
orthogonal to starting the samba server.
I installed Redhat 9 (Shrike) on the test box, and tested samba with
both the vendor kernel and 2.5.67 (with and without SMB_FS before I
realized that was not the issue). It all worked. Then I upgraded
the samba packages (security updates) and tested everything again, and
it still all works.
I cannot reproduce the kernel BUG at fs/buffer.c:2538, at least not yet.
Steven
prev parent reply other threads:[~2003-04-08 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 15:27 Steven Cole
2003-04-08 16:30 ` Helge Hafting
2003-04-08 16:44 ` Steven Cole
2003-04-08 21:16 ` Steven Cole [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=1049836574.32480.1156.camel@spc9.esa.lanl.gov \
--to=elenstev@mesatop.com \
--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
all inboxes | Powered by JetHome®