Re: Regression with FALLOC_FL_PUNCH_HOLE in 3.5-rc kernel
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dne 30.6.2012 21:55, Hugh Dickins napsal(a):
On Sat, 30 Jun 2012, Zdenek Kabelac wrote:When I've used 3.5-rc kernels - I've noticed kernel deadlocks. Ooops log included. After some experimenting - reliable way to hit this oops is to run lvm test suite for 10 minutes. Since 3.5 merge window does not included anything related to this oops I've went for bisect.Thanks a lot for reporting, and going to such effort to find a reproducible testcase that you could bisect on.Game result is commit: 3f31d07571eeea18a7d34db9af21d2285b807a17 mm/fs: route MADV_REMOVE to FALLOC_FL_PUNCH_HOLEBut this leaves me very puzzled. Is the "lvm test suite" what I find at git.fedorahosted.org/git/lvm2.git under tests/ ?
Yes - that's it - make as root: cd test make check_local (inside test subdirectory should be enough, if not - just report any problem)
I see no mention of madvise or MADV_REMOVE or fallocate or anything related in that git tree. If you have something else running at the same time, which happens to use madvise(,,MADV_REMOVE) on a filesystem which the commit above now enables it on (I guess ext4 from the =y in your config), then I suppose we should start searching for improper memory freeing or scribbling in its holepunch support: something that might be corrupting the dm_region in your oops.
What the test is doing - it creates file in LVM_TEST_DIR (default is /tmp) and using loop device to simulate device (small size - it should fit bellow 200MB)Within this file second layer through virtual DM devices is created and simulates various numbers of PV devices to play with.
So since everything now support TRIM - such operations should be passed down to the backend file - which probably triggers the path.
I'll be surprised if that is the case, but it's something that you can easily check by inserting a WARN_ON(1) in mm/madvise.c madvise_remove(): that should tell us what process is using it.
I could try that if that will help.
I'm not an LVM user, so I doubt I'll be able to reproduce your setup.
Shouldn't be hard to run - unsure if every config setup is influnenced or just mine config.
Any ideas from the DM guys? Has anyone else seen anything like this? Do all your oopses look like this one?
I think I've get yet another one - but also within dm_rh_regionIt could be that your patch exposed problem of some different part of stack - not really sure - it's just now with 3.5 this crash will not allow to pass whole test suite - I've tried also in kvm machine and it's been reproducible (so in the worst case I could eventually send you 2GB image)
The problem is - there is not a 'single test case' to trigger the oops (at least I've not figured out one) - it's the combination of multiple tests running after each other - but for simplication this should be enough:
make check_local T=shell/lvconvert Which usually dies on shell/lvconvert-repair-transient.sh Zdenek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Other Archives] [Linux Kernel Newbies] [Linux Driver Development] [Linux Kbuild] [Fedora Kernel] [Linux Kernel Testers] [Linux SH] [Linux Omap] [Linux Tape] [Linux Input] [Linux Kernel Janitors] [Linux Kernel Packagers] [Linux Doc] [Linux Man Pages] [Linux API] [Linux Memory Management] [Linux Modules] [Linux Standards] [Kernel Announce] [Netdev] [Git] [Linux PCI] Linux CAN Development [Linux I2C] [Linux RDMA] [Linux NUMA] [Netfilter] [Netfilter Devel] [SELinux] [Bugtraq] [FIO] [Linux Perf Users] [Linux Serial] [Linux PPP] [Linux ISDN] [Linux Next] [Kernel Stable Commits] [Linux Tip Commits] [Kernel MM Commits] [Linux Security Module] [AutoFS] [Filesystem Development] [Ext3 Filesystem] [Linux bcache] [Ext4 Filesystem] [Linux BTRFS] [Linux CEPH Filesystem] [Linux XFS] [XFS] [Linux NFS] [Linux CIFS] [Ecryptfs] [Linux NILFS] [Linux Cachefs] [Reiser FS] [Initramfs] [Linux FB Devel] [Linux OpenGL] [DRI Devel] [Fastboot] [Linux RT Users] [Linux RT Stable] [eCos] [Corosync] [Linux Clusters] [LVS Devel] [Hot Plug] [Linux Virtualization] [KVM] [KVM PPC] [KVM ia64] [Linux Containers] [Linux Hexagon] [Linux Cgroups] [Util Linux] [Wireless] [Linux Bluetooth] [Bluez Devel] [Ethernet Bridging] [Embedded Linux] [Barebox] [Linux MMC] [Linux IIO] [Sparse] [Smatch] [Linux Arch] [x86 Platform Driver] [Linux ACPI] [Linux IBM ACPI] [LM Sensors] [CPU Freq] [Linux Power Management] [Linmodems] [Linux DCCP] [Linux SCTP] [ALSA Devel] [Linux USB] [Linux PA RISC] [Linux Samsung SOC] [MIPS Linux] [IBM S/390 Linux] [ARM Linux] [ARM Kernel] [ARM MSM] [Tegra Devel] [Sparc Linux] [Linux Security] [Linux Sound] [Linux Media] [Video 4 Linux] [Linux IRDA Users] [Linux for the blind] [Linux RAID] [Linux ATA RAID] [Device Mapper] [Linux SCSI] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Linux IDE] [Linux SMP] [Linux AXP] [Linux Alpha] [Linux M68K] [Linux ia64] [Linux 8086] [Linux x86_64] [Linux Config] [Linux Apps] [Linux MSDOS] [Linux X.25] [Linux Crypto] [DM Crypt] [Linux Trace Users] [Linux Btrace] [Linux Watchdog] [Utrace Devel] [Linux C Programming] [Linux Assembly] [Dash] [DWARVES] [Hail Devel] [Linux Kernel Debugger] [Linux gcc] [Gcc Help] [X.Org] [Wine]
[Older Kernel Discussion] [Yosemite National Park Forum] [Large Format Photos] [Gimp] [Yosemite Photos] [Stuff]