Re: UnionMount status?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 16 August 2010 20:52, Valerie Aurora <vaurora@xxxxxxxxxx> wrote:
> On Wed, Aug 11, 2010 at 12:08:38PM +0200, Michal Suchanek wrote:
>> On 10 August 2010 18:52, Valerie Aurora <vaurora@xxxxxxxxxx> wrote:
>> > On Mon, Jul 19, 2010 at 06:06:36PM +0200, Michal Suchanek wrote:
>> >> On 14 July 2010 21:30, Valerie Aurora <vaurora@xxxxxxxxxx> wrote:
>> >> > On Wed, Jul 14, 2010 at 03:12:28PM +0200, Michal Suchanek wrote:
>> >> >> Hello
>> >> >>
>> >> >> FWIW I tried to apply the unionmount patch from submounts branch to my
>> >> >> kernel (2.6.34 Debian kernel) and boot a live system using the kernel.
>> >> >>
>> >> >> The system boots but locks up during init.
>> >> >>
>> >> >> The first boot method uses tmpfs union/squashfs/loop/FUSE(httpfs) or
>> >> >> tmpfs union/squashfs/loop/iso9660/loop/FUSE(httpfs) and triggers the
>> >> >> BUG_ON(*next_ud != NULL); in union_add_dir when udev starts whereas
>> >> >> the other method which uses tmpfs union/squashfs/loop/iso966/iscsi
>> >> >> crashes because at the point when iscsid is started during boot as the
>> >> >> iscsi drive is disconnected for some reason.
>> >> >
>> >> > Thanks for the bug report! ??I will get to work on that as soon as
>> >> > possible.
>> >> >
>> >> >> As the kernel does not include aufs I cannot easily test that it works
>> >> >> as expected with that but both boot methods used to work with 2.6.32
>> >> >> kernels and aufs.
>> >> >
>> >> > I think it's quite likely the problem is with union mounts, so don't
>> >> > go to the effort to test aufs just for this case.
>> >> >
>> >>
>> >> If you want the live CD or more details about the issue I guess I can send them.
>> >>
>> >> Also the CD build system is automated so it's quite easy to try new patches.
>> >
>> > Can you try the d_ino_lookup branch in the union mounts git tree? ??I
>> > fixed one bug that may be related. ??Thanks,
>> >
>> > -VAL
>> >
>>
>> It does not build for me.
>>
>> Thanks
>>
>> Michal
>>
...
>
> Thanks for attaching your .config.  CONFIG_UNION_MOUNT wasn't set:
>
> # CONFIG_UNION_MOUNT is not set
>
> Try rebuilding with that on.  Yes, it should build without
> CONFIG_UNION_MOUNT and I'll test that for next release.
>
> -VAL
>

Sorry, I thought I enabled it.

Anyway, I changed that option in the config but it still does not build.

Thanks

Michal

  LD      arch/x86/boot/setup.elf
  OBJCOPY arch/x86/boot/setup.bin
  OBJCOPY arch/x86/boot/vmlinux.bin
  HOSTCC  arch/x86/boot/tools/build
  BUILD   arch/x86/boot/bzImage
Root device is (8, 3)
Setup is 14108 bytes (padded to 14336 bytes).
System is 2446 kB
CRC 6af7dba4
Kernel: arch/x86/boot/bzImage is ready  (#5)
  Building modules, stage 2.
  MODPOST 1351 modules
WARNING: drivers/ata/ahci_platform.o(.data+0x0): Section mismatch in
reference from the variable ahci_driver to the function
.init.text:ahci_probe()
The variable ahci_driver references
the function __init ahci_probe()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

WARNING: drivers/net/ksz884x.o(.data+0x30): Section mismatch in
reference from the variable pci_device_driver to the function
.init.text:pcidev_init()
The variable pci_device_driver references
the function __init pcidev_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,

WARNING: drivers/scsi/mpt2sas/mpt2sas.o(.text+0xb140): Section
mismatch in reference from the function _scsih_pci_error_detected() to
the function .devexit.text:_scsih_remove()
The function _scsih_pci_error_detected() references a function in an
exit section.
Often the function _scsih_remove() has valid usage outside the exit section
and the fix is to remove the __devexit annotation of _scsih_remove.

WARNING: net/l2tp/l2tp_eth.o(.exit.text+0x7): Section mismatch in
reference from the function cleanup_module() to the variable
.init.data:l2tp_eth_net_ops
The function __exit cleanup_module() references
a variable __initdata l2tp_eth_net_ops.
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
l2tp_eth_net_ops so it may be used outside an init section.

ERROR: "generic_readdir_fallthru" [fs/ext2/ext2.ko] undefined!
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux