From: Al Viro <viro@ftp.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>, Tomas M <tomas@slax.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] [bugfix] loop.c
Date: Fri, 23 Mar 2007 14:49:12 +0000 [thread overview]
Message-ID: <20070323144912.GB4095@ftp.linux.org.uk> (raw)
In-Reply-To: <20070323144109.GA15114@infradead.org>
On Fri, Mar 23, 2007 at 02:41:09PM +0000, Christoph Hellwig wrote:
> The right thing to start with is to split the allocation up, and allocate
> each loop device by itself, like in the untested patch below:
>
> After that you're not wasting memory for any off number of loop devices
> and can create as many as you have device numbers available:
NAK. You _can't_ bail out in init after add_disk(). It might have been
opened already.
prev parent reply other threads:[~2007-03-23 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 14:04 Tomas M
2007-03-23 14:18 ` Jiri Kosina
2007-03-23 14:19 ` Eric Dumazet
2007-03-23 14:25 ` Jiri Kosina
2007-03-23 14:51 ` Eric Dumazet
2007-03-23 19:50 ` Michael Tokarev
2007-03-23 23:18 ` Jiri Kosina
2007-03-23 14:33 ` William Lee Irwin III
2007-03-23 14:36 ` Al Viro
2007-03-23 14:48 ` Eric Dumazet
2007-03-23 14:56 ` Al Viro
2007-03-23 14:41 ` Christoph Hellwig
2007-03-23 14:49 ` Al Viro [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=20070323144912.GB4095@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas@slax.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®