On Tue, Sep 16, 2014 at 01:05:48PM -0400, Shea Levy wrote:
> On Tue, Sep 16, 2014 at 11:39:57AM -0500, Seth Forshee wrote:
> > On Tue, Sep 16, 2014 at 12:12:47PM -0400, Shea Levy wrote:
> > > OK, compiling with BLK_DEV_LOOP=y (on top of 3.16.2), I was able to
> > > mount loopfs, request a loop devi
On Tue, Sep 16, 2014 at 11:39:57AM -0500, Seth Forshee wrote:
> On Tue, Sep 16, 2014 at 12:12:47PM -0400, Shea Levy wrote:
> > OK, compiling with BLK_DEV_LOOP=y (on top of 3.16.2), I was able to
> > mount loopfs, request a loop device from loop-control, and associate it
> > with an image with an ex
On Tue, Sep 16, 2014 at 12:12:47PM -0400, Shea Levy wrote:
> OK, compiling with BLK_DEV_LOOP=y (on top of 3.16.2), I was able to
> mount loopfs, request a loop device from loop-control, and associate it
> with an image with an ext4 partition with losetup, but mount still gives
> EPERM (all as root
OK, compiling with BLK_DEV_LOOP=y (on top of 3.16.2), I was able to
mount loopfs, request a loop device from loop-control, and associate it
with an image with an ext4 partition with losetup, but mount still gives
EPERM (all as root in a userns started from an unprivileged account). Is
this expected
On Mon, Sep 15, 2014 at 07:20:52PM -0400, Shea Levy wrote:
> Hi Seth,
>
> I applied your patches to 3.15-rc7, and had the same problem, the build
> fails with:
>
> > make[3]: *** No rule to make target `fs/loopfs/loopfs.c', needed by
> > `fs/loopfs/loopfs.o'. Stop.
>
> I've attached the config
Hi Seth,
I applied your patches to 3.15-rc7, and had the same problem, the build
fails with:
> make[3]: *** No rule to make target `fs/loopfs/loopfs.c', needed by
> `fs/loopfs/loopfs.o'. Stop.
I've attached the config I used, I generated it via make allnoconfig and
then enabled MODULES, BLK, B
On Mon, Sep 15, 2014 at 04:38:44PM -0400, Shea Levy wrote:
> Hi,
>
> I wanted to test these patches (to support creating and filling a disk
> image containing a btrfs filesystem and several subvolumes as an
> unprivileged user), but the build fails due to what looks like a missing
> loopfs.c in fs
Hi,
I wanted to test these patches (to support creating and filling a disk
image containing a btrfs filesystem and several subvolumes as an
unprivileged user), but the build fails due to what looks like a missing
loopfs.c in fs/loopfs (or alternatively an erroneous line in
fs/loopfs/Makefile). I b
On Wed, May 28, 2014 at 04:47:24PM -0700, H. Peter Anvin wrote:
> On 05/27/2014 02:58 PM, Seth Forshee wrote:
> >
> > The patches implement a psuedo filesystem for loop devices, which will
> > allow use of loop devices in containters using standard utilities. Under
> > normal use a loopfs mount wi
On 05/27/2014 02:58 PM, Seth Forshee wrote:
>
> The patches implement a psuedo filesystem for loop devices, which will
> allow use of loop devices in containters using standard utilities. Under
> normal use a loopfs mount will initially contain a single device node
> for loop-control which can be
On Wed, 2014-05-28 at 09:10 -0700, Andy Lutomirski wrote:
> On Wed, May 28, 2014 at 12:32 AM, Seth Forshee
> wrote:
> > On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
> >> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
> >> wrote:
> >> > I'm posting these patches in response to t
On Wed, May 28, 2014 at 12:32 AM, Seth Forshee
wrote:
> On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
>> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
>> wrote:
>> > I'm posting these patches in response to the ongoing discussion of loop
>> > devices in containers at [1].
>> >
On Tue, May 27, 2014 at 03:19:15PM -0700, Andy Lutomirski wrote:
> On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
> wrote:
> > I'm posting these patches in response to the ongoing discussion of loop
> > devices in containers at [1].
> >
> > The patches implement a psuedo filesystem for loop devices
On Tue, May 27, 2014 at 2:58 PM, Seth Forshee
wrote:
> I'm posting these patches in response to the ongoing discussion of loop
> devices in containers at [1].
>
> The patches implement a psuedo filesystem for loop devices, which will
> allow use of loop devices in containters using standard utilit
I'm posting these patches in response to the ongoing discussion of loop
devices in containers at [1].
The patches implement a psuedo filesystem for loop devices, which will
allow use of loop devices in containters using standard utilities. Under
normal use a loopfs mount will initially contain a s
15 matches
Mail list logo
