From: Zan Lynx <zlynx@acm.org>
To: Edward Shishkin <edward@namesys.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Vladimir V. Saveliev" <vs@clusterfs.com>,
Dave Hansen <haveblue@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
reiserfs-devel <reiserfs-devel@vger.kernel.org>,
hch <hch@infradead.org>
Subject: Re: [patch] reiser4: do not allocate struct file on stack
Date: Fri, 05 Oct 2007 10:22:38 -0600 [thread overview]
Message-ID: <1191601358.61085.3.camel@localhost> (raw)
In-Reply-To: <470575AE.9060902@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Fri, 2007-10-05 at 03:22 +0400, Edward Shishkin wrote:
> Edward Shishkin wrote:
>
> > Dave Hansen wrote:
> >
> ...
>
> >>
> >> I think that stack allocation is a pretty nasty trick for a structure
> >> that's supposed to be pretty persistent and dynamically allocated, and
> >> is certainly something that needs to get fixed up in a proper way.
> >>
> >>
> >
> > agreed.
> >
> >> This works around the problem for now, but this could potentially cause
> >> more bugs any time we add some member to 'struct file' and depend on its
> >> state being sane anywhere in the VFS. If there's a list anywhere of
> >> merge-stopper reiser4 bugs around, this should probably go in there.
> >>
> >>
> >
> > will be fixed.
> >
>
> The promised fixup is attached.
> Andrew, please apply.
>
> Thanks,
> Edward.
There were several copies of this email, so I picked one. :)
I had the crash with 2.6.23-rc8-mm2, so I applied this patch. Hunk #1
failed, the rest applied with fuzz. I manually applied hunk #1 and
recompiled.
I am now running with 2.6.23-rc8-mm2 + this patch and things seem good.
(Except for some issues with ACPI battery info moving out of proc and
confusing the heck out of HAL and the GNOME power management scripts).
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-10-05 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1190930060.7667.5.camel@localhost>
[not found] ` <20070928013024.c7522542.akpm@linux-foundation.org>
2007-09-28 16:21 ` 2.6.23-rc8-mm2 NULL dereference in __mnt_is_readonly in ftruncate Dave Hansen
2007-09-28 22:39 ` Edward Shishkin
2007-10-04 23:22 ` [patch] reiser4: do not allocate struct file on stack Edward Shishkin
2007-10-05 16:22 ` Zan Lynx [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=1191601358.61085.3.camel@localhost \
--to=zlynx@acm.org \
--cc=akpm@linux-foundation.org \
--cc=edward@namesys.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vs@clusterfs.com \
/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;
as well as URLs for NNTP newsgroup(s).