linux panics when squashfs image created by older squashfs tools is accessed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I tried to repack my Ubuntu live image with squashfs tools from Debian (squashfs-tools 1:4.0-8).
It caused a kernel panic when booting from the repacked image.
It is completely acceptable that the kernel cannot use old suqashfs images but then it should refuse to mount the image, not panic.
It is likely that mounting and accessing a squashfs image would crash a system booted normally from HDD so if I copied this squashfs filesystem to an USB flash and plugged it into an Ubuntu system with automounting enabled it would crash when an application would try to access the drive flash.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
CurrentDmesg:
Date: Wed Aug 3 15:11:42 2011
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
PciMultimedia:
ProcCmdLine: boot=casper initrd=redo-initrd vga=791 quiet splash toram timezone=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.