public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "Andrew Tipton" <andrew@cadre5.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Tmpfs and loop device don't get along
Date: Sat, 02 Feb 2002 10:48:14 +0100	[thread overview]
Message-ID: <m3elk4p63l.fsf@linux.local> (raw)
In-Reply-To: <00fb01c1ab66$2fbc5490$6400a8c0@africa.cadre5.com>
In-Reply-To: <00fb01c1ab66$2fbc5490$6400a8c0@africa.cadre5.com> ("Andrew Tipton"'s message of "Fri, 1 Feb 2002 16:19:50 -0500")

Hi Andrew,

On Fri, 1 Feb 2002, Andrew Tipton wrote:
> If I have an image (initrd.img for example) located on a tmpfs
> filesystem, when I attempt to mount it:
> 
> % mount -o loop /initrd.img /mnt
> ioctl: LOOP_SET_FD: Invalid argument

In the latest 2.4 sources you will find a file
Documentation/filesystems/tmpfs.txt which describes this problem.

> What is the best way to fix this short-term?  I could bypass the
> readpage check in loop_set_fd, or I could add a dummy readpage entry
> to the address_space_operations struct for tmpfs.  Would either of
> these have serious repercussions?

I do not see an easy and clean way so far. The check for readpage is
definitely needed. loop.c does rely on generic_file_{read,write} and
not on the files read and write operations. So IMHO the cleanest way
is to provide readpage et.al. in shmem.c and use generic_file_{read,write}
instead of specialized shmem_{read,write} functions. Unfortunately
this would mean a nontrivial change to the readpage semantics.

Greetings
		Christoph



      reply	other threads:[~2002-02-03 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 21:19 Tmpfs and loop device don't get along Andrew Tipton
2002-02-02  9:48 ` Christoph Rohland [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=m3elk4p63l.fsf@linux.local \
    --to=cr@sap.com \
    --cc=andrew@cadre5.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox