LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Ken Chen" <kenchen@google.com>
To: "devzero@web.de" <devzero@web.de>
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com
Subject: Re: [patch] remove artificial software max_loop limit
Date: Sun, 1 Apr 2007 11:03:15 -0700	[thread overview]
Message-ID: <b040c32a0704011103w4b45423bxffcffc4f960e8581@mail.gmail.com> (raw)
In-Reply-To: <1713627366@web.de>

On 4/1/07, devzero@web.de <devzero@web.de> wrote:
> 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 ?

kernel returns -ENOMEM as an error code if there are no memory left to
initialize loop device.


> should losetup or dmesg tell "out of memory" if there is not
> enough memory left ?

It should, as kernel does pass that info back to app.  Does losetup
check return value of open() syscall?

  reply	other threads:[~2007-04-01 18:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 10:53 devzero
2007-04-01 18:03 ` Ken Chen [this message]
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=b040c32a0704011103w4b45423bxffcffc4f960e8581@mail.gmail.com \
    --to=kenchen@google.com \
    --cc=devzero@web.de \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [patch] remove artificial software max_loop limit' \
    /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

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).