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 <[email protected]>
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- [patch] reiser4: do not allocate struct file on stack
- From: Edward Shishkin <[email protected]>
- [patch] reiser4: do not allocate struct file on stack
- Prev by Date: Re: [PATCH 01/32] Add an ERR_CAST() macro to complement ERR_PTR and co. [try #2]
- Next by Date: Re: [RFC][PATCH] New message-logging API (kprint)
- Previous by thread: [patch] reiser4: do not allocate struct file on stack
- Next by thread: [patch] reiserfs: do not repair wrong journal params
- Index(es):
 |