From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Eyal Lebedinsky <eyal@eyal.emu.id.au>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc1 - unresolved
Date: Thu, 24 Apr 2003 13:27:39 +0200 [thread overview]
Message-ID: <200304241320.52469.m.c.p@wolk-project.de> (raw)
In-Reply-To: <Pine.LNX.4.53L.0304231650300.7085@freak.distro.conectiva>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Wednesday 23 April 2003 21:51, Marcelo Tosatti wrote:
Hi Marcelo,
> I'm sorry for not having looked into it, Marc. My inbox is not a very
> easily manageable thing.
> > Search the archives. I won't post it again and again and again and again
> > ^again^10.
> I will look into the archives. Thank you.
Don't waste your time with searching archives ;) Take the attached ones.
Explaination:
01. export 'proc_get_inode' symbol b/c it's unresolved in
drivers/net/wan/comx.o
Patch by: Andrea Arcangeli
02. export 'panic_notifier_list, panic_timeout' b/c it's unresolved in
ipmi_msghandler.o and ipmi_watchdog.o
Patch by: me
03. If a process cannot exit because it's stuck in eg. a driver, it
doesn't make sense to have the OOM killer kill it repeatedly;
that could lead to a hung system.
Instead, kill another process if the first process we tried to
kill hasn't made any move to exit within 5 seconds. This way
we have a much better chance of recovering the system.
Patch by: Rik van Riel
I can ack that this fixes the silly behaviour of the oom killer if the
patch is _not_ applied. _With_ the patch, it works great.
--
ciao, Marc
[-- Attachment #2: 01_comx-driver-compile-1.patch --]
[-- Type: text/x-diff, Size: 258 bytes --]
--- 2.4.19pre8aa2/fs/proc/root.c.~1~ Fri May 3 02:12:18 2002
+++ 2.4.19pre8aa2/fs/proc/root.c Sat May 4 13:45:30 2002
@@ -145,3 +145,4 @@
EXPORT_SYMBOL(proc_net);
EXPORT_SYMBOL(proc_bus);
EXPORT_SYMBOL(proc_root_driver);
+EXPORT_SYMBOL(proc_get_inode);
[-- Attachment #3: 03_oomkill-do-not-kill-same-process-repeatedly.patch --]
[-- Type: text/x-diff, Size: 886 bytes --]
If a process cannot exit because it's stuck in eg. a driver, it
doesn't make sense to have the OOM killer kill it repeatedly;
that could lead to a hung system.
Instead, kill another process if the first process we tried to
kill hasn't made any move to exit within 5 seconds. This way
we have a much better chance of recovering the system.
Note: this patch applies without offset to both 2.4 and 2.5,
since oom_kill.c hasn't changed since about 2.4.14...
please apply,
Rik
--
Engineers don't grow up, they grow sideways.
http://www.surriel.com/ http://kernelnewbies.org/
===== mm/oom_kill.c 1.11 vs edited =====
--- 1.11/mm/oom_kill.c Fri Aug 16 10:59:46 2002
+++ edited/mm/oom_kill.c Sat Feb 22 17:31:49 2003
@@ -61,6 +61,9 @@
if (!p->mm)
return 0;
+
+ if (p->flags & PF_MEMDIE)
+ return 0;
/*
* The memory size of the process is the basis for the badness.
*/
[-- Attachment #4: 02_ipmi-exported-symbols-fix.patch --]
[-- Type: text/x-diff, Size: 583 bytes --]
--- linux.orig/kernel/ksyms.c Fri Dec 6 09:12:07 2002
+++ linux/kernel/ksyms.c Fri Dec 6 09:13:01 2002
@@ -65,6 +65,8 @@
extern int request_dma(unsigned int dmanr, char * deviceID);
extern void free_dma(unsigned int dmanr);
extern spinlock_t dma_spin_lock;
+extern int panic_timeout;
+
#ifdef CONFIG_MODVERSIONS
const struct module_symbol __export_Using_Versions
@@ -471,6 +471,8 @@
/* misc */
EXPORT_SYMBOL(panic);
+EXPORT_SYMBOL(panic_notifier_list);
+EXPORT_SYMBOL(panic_timeout);
EXPORT_SYMBOL(__out_of_line_bug);
EXPORT_SYMBOL(sprintf);
EXPORT_SYMBOL(snprintf);
next prev parent reply other threads:[~2003-04-24 11:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 18:47 Linux 2.4.21-rc1 Marcelo Tosatti
2003-04-21 19:58 ` Stephan von Krawczynski
2003-04-21 22:49 ` Ben Greear
2003-04-21 23:24 ` Willy Tarreau
2003-04-21 23:10 ` J.A. Magallon
2003-04-21 23:39 ` Linux 2.4.21-rc1 - unresolved Eyal Lebedinsky
2003-04-22 7:15 ` Marc-Christian Petersen
2003-04-23 19:44 ` Bill Davidsen
2003-04-23 19:51 ` Marcelo Tosatti
2003-04-24 11:27 ` Marc-Christian Petersen [this message]
2003-04-24 11:32 ` Marc-Christian Petersen
2003-04-24 11:37 ` Christoph Hellwig
2003-05-06 2:48 ` Mike Fedyk
2003-04-22 3:00 ` Linux 2.4.21-rc1 Corey Minyard
2003-04-22 21:49 ` Marcelo Tosatti
2003-04-22 22:54 ` Corey Minyard
2003-04-22 13:42 ` Geert Uytterhoeven
2003-04-22 17:09 ` Rene Rebe
2003-04-22 19:15 ` Lukasz Trabinski
2003-04-22 22:59 ` J.A. Magallon
2003-04-23 7:59 ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Stelian Pop
2003-04-23 8:08 ` Linux 2.4.21-rc1 Jerome Chantelauze
2003-04-23 15:09 ` Athanasius
2003-04-23 20:46 ` Olaf Hering
2003-04-30 21:30 ` Carl-Daniel Hailfinger
2003-04-25 3:06 ` Lucas Correia Villa Real
2003-06-07 19:35 ` Adrian Bunk
2003-06-11 4:27 ` Lucas Correia Villa Real
2003-04-25 3:13 ` Lucas Correia Villa Real
2003-04-25 14:15 ` Andreas Metzler
2003-04-25 14:27 ` Martin Josefsson
2003-04-25 14:46 ` Andreas Metzler
2003-04-25 16:19 ` Zed Pobre
2003-04-25 16:24 ` Marc-Christian Petersen
2003-05-06 2:57 ` Mike Fedyk
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=200304241320.52469.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=eyal@eyal.emu.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).