From: devzero@web.de
To: linux-kernel@vger.kernel.org
Cc: jdike@addtoit.com
Subject: Re: [patch] remove artificial software max_loop limit
Date: Sun, 01 Apr 2007 12:53:55 +0200 [thread overview]
Message-ID: <1713627366@web.de> (raw)
not sure if this is a real issue and if it`s UML or loop related - but how is low-memory situations being handled when creating loop devices ?
should losetup or dmesg tell "out of memory" if there is not enough memory left ?
i fired up my 2.6.20 UML and tried to create lots of loop-devices.
this crashed my UML very soon , just around 200 devices - then i saw my "mistake" that my UML had only 32MB of RAM.
then i gave my UML mem=256M and now i can setup many more loop-devices, but still crashes in the end:
setting up loop-device 1962 with losetup
Kernel panic - not syncing: do_fork failed in kernel_thread, errno = -11
EIP: 0073:[<ffffe410>] CPU: 0 Not tainted ESP: 007b:b7e6ffb0 EFLAGS: 00000246
Not tainted
EAX: 00000000 EBX: 000072b3 ECX: 00000013 EDX: 000072b3
ESI: 000072af EDI: 00000011 EBP: 00000000 DS: 007b ES: 007b
087e7eac: [<0807ca7b>] notifier_call_chain+0x1d/0x33
087e7ec8: [<08071416>] panic+0x52/0xdd
087e7ee4: [<0805cd74>] kernel_thread+0x5d/0x5f
087e7ef4: [<0808217f>] keventd_create_kthread+0x1a/0x48
087e7ef8: [<080820cb>] kthread+0x0/0x9a
087e7f10: [<0807f5fb>] run_workqueue+0x8a/0x11f
087e7f18: [<08082165>] keventd_create_kthread+0x0/0x48
087e7f1c: [<08068351>] set_signals+0x1d/0x32
087e7f2c: [<0807f690>] worker_thread+0x0/0x14e
087e7f30: [<0807f7a1>] worker_thread+0x111/0x14e
087e7f74: [<0806e771>] default_wake_function+0x0/0x12
087e7f98: [<0808213f>] kthread+0x74/0x9a
087e7fbc: [<080679bf>] run_kernel_thread+0x38/0x41
087e7fd8: [<080679a2>] run_kernel_thread+0x1b/0x41
087e7fe4: [<0805f92f>] new_thread_handler+0x53/0x79
087e7fe8: [<080820cb>] kthread+0x0/0x9a
regards
roland
> -----Ursprüngliche Nachricht-----
> Von: devzero@web.de
> Gesendet: 01.04.07 11:16:14
> An: linux-kernel@vger.kernel.org
> Betreff: Re: [patch] remove artificial software max_loop limit
> >Remove artificial maximum 256 loop device that can be created due to a
> >legacy device number limit. Searching through lkml archive, there are
> >several instances where users complained about the artificial limit
> >that the loop driver impose. There is no reason to have such limit.
>
> Hey, i was one of those :)
>
> Nice to see, that it`s solved now, thanks very much!
>
> I never expected this to happen and put all my hope into dm-loop instead.
> Did you mind that Bryn m. Reeves from redhat will suffer a serious depression now? ( -> http://sources.redhat.com/lvm2/wiki/DMLoop ) ;)
>
> regards
> roland
>
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
next reply other threads:[~2007-04-01 10:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 10:53 devzero [this message]
2007-04-01 18:03 ` [patch] remove artificial software max_loop limit Ken Chen
2007-04-01 19:00 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2007-04-01 18:54 devzero
2007-04-01 18:36 devzero
2007-04-01 18:43 ` Kyle Moffett
2007-04-01 9:16 devzero
2007-03-30 7:53 Ken Chen
2007-03-30 8:48 ` Ken Chen
2007-03-30 9:07 ` Jan Engelhardt
2007-03-30 9:25 ` Ken Chen
2007-03-30 16:16 ` Jan Engelhardt
2007-03-30 21:15 ` Andrew Morton
2007-03-30 22:06 ` Ken Chen
2007-03-30 22:50 ` Andrew Morton
2007-03-31 17:07 ` Greg KH
2007-03-31 17:41 ` Andrew Morton
2007-04-01 4:16 ` Ken Chen
2007-04-04 10:31 ` Tomas M
2007-04-04 18:47 ` Andrew Morton
2007-04-01 16:53 ` Tomas M
2007-04-01 16:57 ` Tomas M
2007-04-01 18:10 ` Ken Chen
2007-04-01 19:06 ` Jan Engelhardt
2007-04-06 20:33 ` Bill Davidsen
2007-04-07 16:18 ` Valdis.Kletnieks
2007-04-07 16:34 ` Bill Davidsen
2007-03-30 21:46 ` Andrew Morton
2007-03-30 21:52 ` Jan Engelhardt
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=1713627366@web.de \
--to=devzero@web.de \
--cc=jdike@addtoit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.