From: Andrew Morton <akpm@osdl.org>
To: franz_pletz@t-online.de, axboe@suse.de,
linux-kernel@vger.kernel.org, ludoschmidt@web.de
Subject: Re: [PATCH] loopback device can't act as its backing store
Date: Fri, 3 Dec 2004 14:51:40 -0800 [thread overview]
Message-ID: <20041203145140.002e338f.akpm@osdl.org> (raw)
In-Reply-To: <20041203145056.541308d1.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> Andries posted such a patch
Begin forwarded message:
Date: Sun, 14 Nov 2004 23:31:21 +0100 (MET)
From: <Andries.Brouwer@cwi.nl>
To: akpm@osdl.org, lkml@happyjack.org, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH?] prevent loop infinite recursion
After "losetup /dev/loop0 /dev/loop0" I see a hard crash upon
access of /dev/loop0. And of course the same happens after
"losetup /dev/loop0 /dev/loop1; "losetup /dev/loop1 /dev/loop0"
Chris Spiegel reports a slightly different crash doing similar things.
The easiest fix is saying "don't do that then".
The patch below adds a (somewhat ugly) test for recursion.
Maybe someone can think of a nicer version.
Andries
diff -uprN -X /linux/dontdiff a/drivers/block/loop.c b/drivers/block/loop.c
--- a/drivers/block/loop.c 2004-08-26 22:05:15.000000000 +0200
+++ b/drivers/block/loop.c 2004-11-14 22:43:31.000000000 +0100
@@ -622,10 +622,17 @@ static int loop_change_fd(struct loop_de
return error;
}
+static inline int is_loop_device(struct file *file)
+{
+ struct inode *i = file->f_mapping->host;
+
+ return i && S_ISBLK(i->i_mode) && MAJOR(i->i_rdev) == LOOP_MAJOR;
+}
+
static int loop_set_fd(struct loop_device *lo, struct file *lo_file,
struct block_device *bdev, unsigned int arg)
{
- struct file *file;
+ struct file *file, *f;
struct inode *inode;
struct address_space *mapping;
unsigned lo_blocksize;
@@ -636,15 +643,28 @@ static int loop_set_fd(struct loop_devic
/* This is safe, since we have a reference from open(). */
__module_get(THIS_MODULE);
- error = -EBUSY;
- if (lo->lo_state != Lo_unbound)
- goto out;
-
error = -EBADF;
file = fget(arg);
if (!file)
goto out;
+ error = -EBUSY;
+ if (lo->lo_state != Lo_unbound)
+ goto out_putf;
+
+ /* Avoid recursion */
+ f = file;
+ while (is_loop_device(f)) {
+ struct loop_device *l;
+
+ if (f->f_mapping->host == lo_file->f_mapping->host)
+ goto out_putf;
+ l = f->f_mapping->host->i_bdev->bd_disk->private_data;
+ if (l->lo_state == Lo_unbound)
+ break;
+ f = l->lo_backing_file;
+ }
+
mapping = file->f_mapping;
inode = mapping->host;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-12-03 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 19:51 [PATCH] loopback device can't act as its backing store Franz Pletz
2004-12-03 21:42 ` Phil Oester
2004-12-03 22:31 ` Franz Pletz
2004-12-03 22:50 ` Andrew Morton
2004-12-03 22:51 ` Andrew Morton [this message]
2004-12-04 0:34 ` Franz Pletz
[not found] <fa.gge7q0c.1pjgej6@ifi.uio.no>
[not found] ` <fa.gbb6job.1um2er1@ifi.uio.no>
2004-12-04 0:25 ` Bodo Eggert
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=20041203145140.002e338f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=franz_pletz@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ludoschmidt@web.de \
/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