Bug#1040901: Upcoming changes to Debian Linux kernel packages
On Thu, Oct 26, 2023 at 01:36:50PM +0200, Bastian Blank wrote: > On Fri, Oct 20, 2023 at 05:54:23PM +0200, Bastian Blank wrote: > > Or would it be easier to re-use normal dependency resolving, like: > > Kernel-Provides: linux (>> 6.6.1~), linux (<< 6.6.1.) > > This would allow full flexibility and re-uses existing code to check > > such definitions. > > Okay, noone complained, so it looks like this should work. > No no it doesn't. Did nobody read my email? Did I even send my email? I don't know what the hell is going on here, but I spend an hour writing an email discussing the options outlined before this ridiculousness and the requirements, but I can't find it in my notmuch. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1040901: Upcoming changes to Debian Linux kernel packages
OK, it seems my original email got lost somewhere in tech hickups, it's possible the kernel crashed before sending the email, AMD just crashes once or twice a day. So I'm writing this email a bit in a hurry, so it's not quite as thought out as the last one weeks ago, but yesterday's email was pretty concerning. We should not rush this. we need to be realistic that this will take a couple of months to sort out a new scheme, don't expect this to be done before the end of the year, and that seems to be very optimistic. On Sat, Oct 07, 2023 at 04:53:33PM +0200, Bastian Blank wrote: > Moin > > On Sun, Sep 24, 2023 at 03:01:51PM +0200, Bastian Blank wrote: > > ## Kernel modules will be signed with an ephemeral key > > This is now > https://salsa.debian.org/kernel-team/linux/-/merge_requests/607. > > > ## Image packages contains more version info > > > > Example: linux-image-6.5.3-cloud-arm64 > > > It will not longer be possible to reliably derive the package name from > > kernel release (see above), as both values are not really related > > anymore. This package name seems to be missing the Debian release, which is mandatory to ensure that you can install 6.5.3-2 and 6.5.3-1 in parallel, which again is mandatory. That's not something we can compromise on; it's absolutely vital that - you can revert to the kernel you last booted succesfully, i.e. 6.5.3-1 if 6.5.3-2 is broken (think toolchain broke or something on buildds) - the currently booted kernel is not impacted. This means it must be able to load additional modules. Some platforms even require additional modules to be loaded to reboot, I've seen this on laptops. It is fine to say "you must reboot", but it is not fine to just break the running system until you do. > > I missed that apt does something similar (maintainers cced). It wants > to see if a particular package matches the current kernel to make the > autoremove prevention work. That lookup is quite a hard problem. > > What should work: We define a new control field. It contains both the > kernel name and a version prefix. > > Example: > - Linux 6.6 (would match 6.6-1, 6.6.1-1) > - Linux 6.6.3 (would match 6.6.3-1, but not 6.6.3+2-1) > - Linux 6.6.3+2 > > The algorithm would be something like this: > - Check $(uname -s) against the first word. Otherwise completely > ignore. Needless to say I do not believe that uname -s is necessarily a single word. > - Check if $(uname -r) matches the version prefix in this field. Mark > as keep if it matches. > - Aggregate packages by version prefix. > - Sort as version, keep newest two(?). I don't really care about the ordering, I want to order by package version. I need to identify: * Which kernel image package is currently booted. Hence I need to go from the uname -r to exactly one installed kernel image package that acts as the key package to determine if a kernel version is installed. * What are other installed kernel image packages * Given a uname / kernel image package, which other kernel packages belong to it This allows me to keep the currently installed kernels around. The flip side of the coin is the code in APT that actually autoremoves kernels: It needs to identify, given a list of kernel images to keep which other kernel packages can be removed. Optimally it can still remove headers for 6.6 if you don't even have 6.6 images installed anymore and _somehow_ pulled them in. Essentially I want to order kernel image packages by version, and keep the currently booted and the latest one, and the 2nd latest if currently booted == latest one, and then remove any other versioned kernel package not related to them. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Re: How to revoke Debian kernels for secure boot
On Wed, Dec 13, 2023 at 10:18:40PM +, Dimitri John Ledkov wrote: > At the moment the best options are: > > - rotate online signing key > - build new shim with old signing key in vendorx (revoked ESL) > - build new kernels with old signing key built-in revoked keyring > > This is to ensure that old shim & old kernel can boot or kexec new kernels. > To ensure new shim cannot boot old kernels. > To ensure that new kernels cannot kexec old kernels. > > This is revocation strategy used by Canonical Kernel Team for Ubuntu > Kernels. > > There is no sbat for kernels yet (and/or nobody has yet started to use sbat > for kernels). Reading this summary also made me realize that if we do SBAT for kernels and want to rely it, we also need to make kernels *check* SBAT so that it is respected at kexec. This can be done two ways: - You do an SBAT self-check at startup to see if you are revoked yourself, which is what shim does - You check the SBAT of the kernel you are about to kexec I'd generally prefer the self-check I think because that also applies if you boot kernels via UEFI directly or something. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1064838: New package names break APT safety features, ability to co-install different ABIs
Source: linux Severity: serious X-Debbugs-Cc: j...@debian.org After we had discussed the new proposal a couple months ago and were left with severe open questions and concerns it seems that these have been ignored and the packages uploaded anyway, breaking APT's algorithm that ensures the currently booted kernel is not offered for removal, as well as possibly others. In addition, this means that the ABI changes within the same package names, causing different ABIs to no longer be co-installable, which can have drastic effect on thef function of systems: - modules will fail to load until you reboot - modules needed to reboot will fail to load until you reboot (if any) I do not believe fucking up our users for convenience of the maintainers and lacking of tools on the ftpmaster side to automatically approve new ABI renames is the right call here. As such if this change is not reverted, I intend to reassign this to the technical committee for deliberation. -- System Information: Debian Release: trixie/sid APT prefers noble APT policy: (500, 'noble'), (500, 'mantic-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.0-11-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1064838: New package names break APT safety features, ability to co-install different ABIs
On Mon, Feb 26, 2024 at 02:20:41PM +0100, Julian Andres Klode wrote: > Source: linux > Severity: serious > X-Debbugs-Cc: j...@debian.org > > After we had discussed the new proposal a couple months ago and were > left with severe open questions and concerns it seems that these have > been ignored and the packages uploaded anyway, breaking APT's algorithm > that ensures the currently booted kernel is not offered for removal, as > well as possibly others. > > In addition, this means that the ABI changes within the same package > names, causing different ABIs to no longer be co-installable, which can > have drastic effect on thef function of systems: > > - modules will fail to load until you reboot > - modules needed to reboot will fail to load until you reboot (if any) > > I do not believe fucking up our users for convenience of the maintainers > and lacking of tools on the ftpmaster side to automatically approve new > ABI renames is the right call here. > > As such if this change is not reverted, I intend to reassign this to > the technical committee for deliberation. This is a followup to the discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040901 which we discussed all this in October all these concerns were already raised in, and lots of open questions remained that we were nowhere near ready to do this even if we all agreed that was the right move. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1064839: Consider not using an ephemeral key or document its security model
Source: linux Severity: normal X-Debbugs-Cc: j...@debian.org In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040901 I asked you to switch to an ephemeral key which was a misunderstanding from a discussion with xnox, which we still need to sort out fully. Please either document how the buildds ensure that - private key generation has enough, and high quality enough, entropy - private keys are safely erased after not being needed anymore or revert to signing modules with the CA key and use MODVERSIONS and co to ensure that modules built for one ABI cannot be used with another. I need to update the question in shim-review accordingly, I think I never reverted it or adjusted it, but it will likely take the form of the previous three paragraphs. I sincerely apologize for causing this misunderstanding. -- System Information: Debian Release: trixie/sid APT prefers noble APT policy: (500, 'noble'), (500, 'mantic-security') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.0-11-generic (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Re: [PATCH v2] builddeb: Support signing kernels with the module signing key
On Mon, Feb 07, 2022 at 09:33:46PM +0900, Masahiro Yamada wrote:
> Added "Ben Hutchings "
>
> On Wed, Jan 5, 2022 at 3:13 AM Matthew Wilcox wrote:
> >
> > On Wed, Jan 05, 2022 at 12:39:57AM +0900, Masahiro Yamada wrote:
> > > > +vmlinux=$($MAKE -s -f $srctree/Makefile image_name)
> > > > +key=
> > > > +if is_enabled CONFIG_EFI_STUB && is_enabled CONFIG_MODULE_SIG; then
> > > > + cert=$(grep ^CONFIG_MODULE_SIG_KEY= include/config/auto.conf |
> > > > cut -d\" -f2)
> > > > + if [ ! -f $cert ]; then
> > > > + cert=$srctree/$cert
> > > > + fi
> > > > +
> > > > + key=${cert%pem}priv
> > > > + if [ ! -f $key ]; then
> > > > + key=$cert
> > > > + fi
> > >
> > >
> > > I still do not understand this part.
> > >
> > > It is true that the Debian document you referred to creates separate files
> > > for the key and the certificate:
> > > # openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform
> > > DER -out MOK.der -days 36500 -subj "/CN=My Name/" -nodes
> > >
> > > but, is such a use-case possible in Kbuild?
> >
> > If someone has followed the Debian instructions for creating a MOK,
> > then they will have two separate files. We should support both the case
> > where someone has created a Debian MOK and the case where someone has
> > used Kbuild to create this foolish blob with both private and public
> > key in one file.
>
> But, this patch is doing different things than the Debian document.
>
>
> The Debian document you referred to says:
> "Ubuntu puts its MOK key under /var/lib/shim-signed/mok/ and some
>software such as Oracle's virtualbox package expect the key there
>so we follow suit (see 989463 for reference) and put it at the same place"
>
>
>
> In Debian, MOK is generated under /var/lib/shim-signed/mok/,
> and its primary use is for signing the kernel.
> Then, you can reuse it for signing modules as well.
It's worth pointing out that in Ubuntu, the generated MOK key
is for module signing only (extended key usage 1.3.6.1.4.1.2312.16.1.2),
kernels signed with it will NOT be bootable.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Re: [PATCH v2] builddeb: Support signing kernels with the module signing key
On Tue, Feb 08, 2022 at 01:10:34PM +, Matthew Wilcox wrote: > On Tue, Feb 08, 2022 at 12:01:22PM +0100, Julian Andres Klode wrote: > > It's worth pointing out that in Ubuntu, the generated MOK key > > is for module signing only (extended key usage 1.3.6.1.4.1.2312.16.1.2), > > kernels signed with it will NOT be bootable. > > Why should these be separate keys? There's no meaningful security > boundary between a kernel module and the ernel itself; a kernel > modulecan, for example, write to CR3, and that's game over for > any pretence at separation. I don't really _know_, but I believe the difference is that the kernel binaries runs in boot services, and calls ExitBootServices, whereas modules are loaded after ExitBootServices. But I don't know the full rationale why (a) the feature exists in the first place and (b) why the Ubuntu security team chose to require that constraint. My goal is just to make people aware of that so they can make informed decisions :) -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload
Source: linux Version: 6.3.0-7.7 Severity: grave Tags: security X-Debbugs-Cc: j...@debian.org I know there's some work in progress but it appears we don't have a bug for it yet. I raised this yesterday in our weekly upstream shim/grub cabal meetings and Debian's current approach to sign modules with the same key and not bump ABI on every upload should be considered a bug. The current approach means that a kernel cannot be easily revoked, you would need to add its kernel modules to the dbx as well, which is a grave security bug. The state of the art solution is to sign everything using an ephemeral key, which yes, it will cause the package to be unreproducible, but if nobody commits to working on that merkle tree of modules, than this is very well going to have to be the solution to the issue. A reasonable compromise at a first step for a limited time is to ensure that 1) the kernel refuses to load modules for a different ABI in lockdown, for example, the modprobe --force-vermagic does not work anymore. 2) each upload bumps the ABI [this is also required for the ephemeral key and merkle tree approaches as otherwise the modules become no longer loadable] This is still somewhat problematic as there may be bugs in the code validating parsing the kernel module sections that could be exploited if there were some weird modules, but it's a significant improvement (turning this from grave to serious I guess). -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload
Control: notfound -1 6.3.0-7.7 On Wed, Jul 12, 2023 at 10:05:03AM +0200, Julian Andres Klode wrote: > Source: linux > Version: 6.3.0-7.7 > Severity: grave > Tags: security > X-Debbugs-Cc: j...@debian.org Sorry about that, it picked up the version from my work system's Ubuntu kernel and I forgot to clean it. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#1040901: linux modules must not be signed with CA key, bump ABI every upload
On Wed, Jul 12, 2023 at 10:05:03AM +0200, Julian Andres Klode wrote: > Source: linux > Version: 6.3.0-7.7 > Severity: grave > Tags: security > X-Debbugs-Cc: j...@debian.org > > I know there's some work in progress but it appears we don't have a bug > for it yet. I raised this yesterday in our weekly upstream shim/grub > cabal meetings and Debian's current approach to sign modules with the > same key and not bump ABI on every upload should be considered a bug. FWIW, I'm adding this formally as a requirement to the shim-review process in https://github.com/rhboot/shim-review/pull/337 So that we do not accidentally accept submissions with this bug anymore. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Bug#611555: initramfs-tools: Modules needed for btrfs not included in initramfs
Package: initramfs-tools Version: 0.98.8 Severity: important The btrfs module depends on libcrc32c which requires a crc32c provider like crc32c, but does not specify it in depends; and the module is thus not included. The result is that if you choose to install with / formatted as btrfs, the installation is not able to boot. A possible solution is to include the crc32c module whenever a module requests libcrc32c. -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initramfs-tools depends on: ii cpio 2.11-6 GNU cpio -- a program to manage ar ii findutils 4.4.2-1+b1 utilities for finding files--find, ii klibc-utils 1.5.21-1 small utilities built with klibc f ii module-init-tools 3.12-1 tools for managing Linux kernel mo ii udev 164-4 /dev/ and hotplug management daemo Versions of packages initramfs-tools recommends: ii busybox 1:1.17.1-8 Tiny utilities for small and embed Versions of packages initramfs-tools suggests: ii bash-completion 1:1.2-3programmable completion for the ba -- Configuration Files: /etc/kernel/postinst.d/initramfs-tools changed [not included] -- no debconf information -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpZdPJpq2VqX.pgp Description: PGP signature
Bug#811352: linux 4.4-rc8: i915: "[drm] stuck on render ring" on resume
0-2 Versions of packages linux-image-4.4.0-rc8-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.03+dfsg-11 pn linux-doc-4.4 Versions of packages linux-image-4.4.0-rc8-amd64 is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi20160110-1 pn firmware-libertas pn firmware-linux pn firmware-linux-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink ii firmware-realtek 20160110-1 pn xen-hypervisor -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you. -- Logs begin at Wed 2015-11-25 20:44:40 CET, end at Mon 2016-01-18 08:58:13 CET. -- Jan 18 08:55:11 jak-x230 kernel: PM: Syncing filesystems ... done. Jan 18 08:55:11 jak-x230 kernel: PM: Preparing system for sleep (mem) Jan 18 08:55:11 jak-x230 kernel: (NULL device *): firmware: direct-loading firmware iwlwifi-6000g2a-6.ucode Jan 18 08:55:11 jak-x230 kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Jan 18 08:55:11 jak-x230 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 18 08:55:11 jak-x230 kernel: PM: Suspending system (mem) Jan 18 08:55:11 jak-x230 kernel: Suspending console(s) (use no_console_suspend to debug) Jan 18 08:55:11 jak-x230 kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jan 18 08:55:11 jak-x230 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Jan 18 08:55:11 jak-x230 kernel: sd 2:0:0:0: [sdb] Stopping disk Jan 18 08:55:11 jak-x230 kernel: sd 0:0:0:0: [sda] Stopping disk Jan 18 08:55:11 jak-x230 kernel: e1000e: EEE TX LPI TIMER: 0011 Jan 18 08:55:11 jak-x230 kernel: PM: suspend of devices complete after 653.472 msecs Jan 18 08:55:11 jak-x230 kernel: PM: late suspend of devices complete after 15.980 msecs Jan 18 08:55:11 jak-x230 kernel: ehci-pci :00:1d.0: System wakeup enabled by ACPI Jan 18 08:55:11 jak-x230 kernel: ehci-pci :00:1a.0: System wakeup enabled by ACPI Jan 18 08:55:11 jak-x230 kernel: xhci_hcd :00:14.0: System wakeup enabled by ACPI Jan 18 08:55:11 jak-x230 kernel: PM: noirq suspend of devices complete after 19.888 msecs Jan 18 08:55:11 jak-x230 kernel: ACPI: Preparing to enter system sleep state S3 Jan 18 08:55:11 jak-x230 kernel: ACPI : EC: EC stopped Jan 18 08:55:11 jak-x230 kernel: PM: Saving platform NVS memory Jan 18 08:55:11 jak-x230 kernel: Disabling non-boot CPUs ... Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 30 Jan 18 08:55:11 jak-x230 kernel: smpboot: CPU 1 is now offline Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 25 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 28 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 30 Jan 18 08:55:11 jak-x230 kernel: smpboot: CPU 2 is now offline Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 1 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 9 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 12 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 16 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 23 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 24 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 25 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 28 Jan 18 08:55:11 jak-x230 kernel: Broke affinity for irq 30 Jan 18 08:55:11 jak-x230 kernel: smpboot: CPU 3 is now offline Jan 18 08:55:11 jak-x230 kernel: ACPI: Low-level resume complete Jan 18 08:55:11 jak-x230 kernel: ACPI : EC: EC started Jan 18 08:55:11 jak-x230 kernel: PM: Restoring platform NVS memory Jan 18 08:55:11 jak-x230 kernel: Enabling non-boot CPUs ... Jan 18 08:55:11 jak-x230 kernel: x86: Booting SMP configuration: Jan 18 08:55:11 jak-x230 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 Jan 18 08:55:11 jak-x230 kernel: cache: parent cpu1 should not be sleeping Jan 18 08:55:11 jak-x230 kernel: CPU1 is up Jan 18 08:55:11 jak-x230 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 Jan 18 08:55:11 jak-x230 kernel: cache: parent cpu2 should not be sleeping Jan 18 08:55:11 jak-x230 kernel: CPU2 is up Jan 18 08:55:11 jak-x230 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 Jan 18 08:55:11 jak-x230 kernel: cache: parent cpu3 should not be sleeping Jan 18 08:55:11 jak-x230 kernel: CPU3 is up Jan 18 08:55:11 jak-x230 kernel: ACPI: Waking up from system sleep state S3 Jan 18 08:55:11 jak-x230 kernel: ehci-pci :00:1d.0: System wakeup disabled by ACPI Jan 18 08:55:11 jak-x230 kernel: sdhci-pci :02:00.0: MMC controller base frequency changed to 50Mhz. Jan
Bug#811352: linux 4.4-rc8: i915: "[drm] stuck on render ring" on resume
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92998 Control: tag -1 upstream On Mon, Jan 18, 2016 at 09:21:50AM +0100, Julian Andres Klode wrote: > Package: src:linux > Version: 4.4~rc8-1~exp1 > Severity: normal > > I'm not sure if that's the right package to report this bug, it could > also be mesa, the X11 driver, or maybe even gnome-shell. Anyway, I don't > think I have seen this with 4.3: > > Often, when resuming the GPU hangs, and gnome-shell thus exits and then > restarts, delaying usable resume by about 13 seconds. > > I'm running xserver-xorg-video-intel 2.99.917+git20151217-1~exp1 from > experimental (as unstable has a few bugs fixed in there), and libdrm > 2.4.65-3. Neither have been upgraded recently, so it is > likely the kernel causing the issue, as this is a very recent > problem. This seems to be https://bugs.freedesktop.org/show_bug.cgi?id=92998, which is caused by commit 101b506a7fc7be3f0d0a337ade270eb5eb5a2857: drm/i915: Wa32bitGeneralStateOffset & Wa32bitInstructionBaseOffset at least according to some comments in the bug report. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#727243: linux: 3.11: aufs: au_loopback_init:136:modprobe[24614]: loop_backing_file() is not defined
devices: Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 004: ID 5986:02d2 Acer, Inc Bus 003 Device 018: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (980, 'unstable'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.11-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.51 ii initramfs-tools [linux-initramfs-tool] 0.114 ii kmod9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.11-1-amd64 recommends: pn firmware-linux-free Versions of packages linux-image-3.11-1-amd64 suggests: pn debian-kernel-handbook pn grub-pc | extlinux | lilo pn linux-doc-3.11 Versions of packages linux-image-3.11-1-amd64 is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi0.40 pn firmware-libertas pn firmware-linux pn firmware-linux-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink ii firmware-realtek 0.40 pn xen-hypervisor -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131023195447.ga28...@debian.org
Bug#741989: linux: 3.13.5: known regression: "xHCI xhci_drop_endpoint called with disabled ep"
6]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Device [17aa:21fa] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04) Subsystem: Lenovo Device [17aa:21fa] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: sdhci-pci 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] [8086:0085] (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1311] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi ** USB devices: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 5986:02d2 Acer, Inc Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 015: ID 8564:1000 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (980, 'unstable'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.13-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.52 ii initramfs-tools [linux-initramfs-tool] 0.115 ii kmod16-2 ii linux-base 3.5 ii module-init-tools 16-2 Versions of packages linux-image-3.13-1-amd64 recommends: ii firmware-linux-free 3.3 Versions of packages linux-image-3.13-1-amd64 suggests: pn debian-kernel-handbook pn grub-pc | extlinux | lilo pn linux-doc-3.13 Versions of packages linux-image-3.13-1-amd64 is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi0.41 pn firmware-libertas pn firmware-linux pn firmware-linux-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink ii firmware-realtek 0.41 pn xen-hypervisor -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140318001252.ga1...@debian.org
Bug#741989: linux: 3.13.5: known regression: "xHCI xhci_drop_endpoint called with disabled ep"
On Tue, Mar 18, 2014 at 12:20:18AM +0100, Julian Andres Klode wrote: > Package: src:linux > Version: 3.13.5-1 > Severity: normal > > 3.13.5 introduces a regression in the xhci code that causes mass > storage to not work correctly. In my case, the experience was that > first writes failed misteriously, the filesystem was corrupted > and then it could not be mounted anymore and I saw I/O errors. It might even cause data loss. If the disks can get mounted and we start a write, some things could get lost or the disk corrupted, given that the FAT on my USB stick was corrupted after writing to it. So the bug should probably be RC. > > The problem seems to be known upstream > > https://lkml.org/lkml/2014/3/6/284 > > and fixed in 3.14-rc6. I hope the relevant commits (reverts) > will be backported to 3.13.7. If a stable release includes: > Revert "xhci 1.0: Limit arbitrarily-aligned scatter gather." > this most likely means that this bug is fixed. As far as I can tell, the needed revert commits are precisely: e2ed511400d41e0d136089d5a55ceab57c6a2426 Revert "xhci 1.0: Limit arbitrarily-aligned scatter gather." 469d417b68958a064c09e7875646c97c6e783dfc Revert "USBNET: ax88179_178a: enable tso if usb host supports sg dma" -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140318002231.ga2...@debian.org
Bug#723767: linux: 3.11 Failed to suspend: RCU stall, soft lock-ups
On Thu, Sep 19, 2013 at 06:37:59PM +0200, Julian Andres Klode wrote:
> Package: src:linux
> Version: 3.11-1~exp1
> Severity: important
>
> I today tried to suspend my ThinkPad X230, but apparently this did not
> work. 20 seconds after "PM: Preparing system for mem sleep", I get a
> " INFO: rcu_sched self-detected stall on CPU { 0}" and then several
> soft lockup messages. Rebooting did not fix the no-sleep problem, I
> removed the battery for 10 seconds, that fixed it (the UEFI system
> or the hardware itself might have been confused by the kernel bug).
>
> When experiencing the bug, the system looked as if it suspended correctly
> at first; but after a few seconds; the system was completely active
> again.
This resume problem still exists. Seems like something is waking up
the system again immediately after suspend. I can't find anything
suspicious in the kernel log.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
pgp1pERcBbgYi.pgp
Description: PGP signature
Bug#723767: linux: 3.11 Failed to suspend: RCU stall, soft lock-ups
kmod9-3 ii linux-base 3.5 ii module-init-tools 9-3 Versions of packages linux-image-3.11-trunk-amd64 recommends: pn firmware-linux-free Versions of packages linux-image-3.11-trunk-amd64 suggests: pn debian-kernel-handbook pn grub-pc | extlinux | lilo pn linux-doc-3.11 Versions of packages linux-image-3.11-trunk-amd64 is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi0.40 pn firmware-libertas pn firmware-linux pn firmware-linux-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink ii firmware-realtek0.40 pn xen-hypervisor -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. kern.edited.log.xz Description: Binary data pgpEH1LyCcFrr.pgp Description: PGP signature
Bug#630474: linux 3.0 package names should probably not include SUBLEVEL
SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlagn 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03) Subsystem: Lenovo Device [17aa:2131] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: r8169 ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02) Subsystem: Lenovo Device [17aa:2196] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- (no description available) Versions of packages linux-image-3.0.0-rc2-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.30 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink(no description available) pn xen-hypervisor (no description available) -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpd2TmpkLjCZ.pgp Description: PGP signature
Bug#630474: linux 3.0 package names should probably not include SUBLEVEL
On Tue, 2011-06-14 at 12:00 +, maximilian attems wrote: > On Tue, Jun 14, 2011 at 12:41:13PM +0200, Julian Andres Klode wrote: > > Package: linux-2.6 > > Version: 3.0.0~rc2-1~experimental.1 > > Severity: normal > > > > SUBLEVEL is reserved for -stable in kernel 3.0 and > > newer. As Debian kernels did not include the part > > of the version number used for stable updates in > > the past, I expect that you are not planning to > > include them now. > > > > Thus, the package names should be linux-image-3.0-*, > > not linux-image-3.0.0-*. > > no. > next time ask on d-kernel for advise before filing useless reports. Then please explain why. The kernel's version is 3.0, not 3.0.0. Once there is 3.0.X, do you want to introduce new linux-image-3.0.X-* packages every few weeks? There appears to be no reason for using 3.0.0, upstream uses 3.0, others use 3.0, so why deviate? If you are worried about userspace compatibility, then those are bugs and have to be fixed elsewhere (and the kernel packages changed afterwards). -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1308057988.7375.7.camel@jak-thinkpad
Bug#635007: linux-2.6: Removing USB connection crashes usbnet, USB hotplugging
no description available) ii firmware-iwlwifi 0.32 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink(no description available) pn xen-hypervisor (no description available) -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpJBEHRbbtWE.pgp Description: PGP signature
Bug#854880: firmware-atheros ships binary ath9k_htc firmwares containing GPL code
Package: firmware-atheros
Severity: serious
The binary files
Files: ath9k_htc/htc_7010-1.4.0.fw, ath9k_htc/htc_9271-1.4.0.fw
were created from files that include GPL components according to
the copyright file, specially, the eCos files:
eCos is free software; you can redistribute it and/or modify it under
the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 or (at your option) any later version.
.
As a special exception, if other files instantiate templates or use macros
or inline functions from this file, or you compile this file and link it
with other works to produce a work based on this file, this file does not
by itself cause the resulting work to be covered by the GNU General Public
License. However the source code for this file must still be made available
in accordance with section (3) of the GNU General Public License.
.
This exception does not invalidate any other reasons why a work based on
this file might be covered by the GNU General Public License.
These need to be either added to the package or the firmware needs
to be removed from the archive.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (500, 'testing'), (100, 'experimental'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Bug#859570: linux 4.10: Please enable CONFIG_BLK_WBT?
Source: linux
Version: 4.10-1~exp1
Severity: wishlist
I think it makes sense to enable writeback throttling. I often see systems
basically locking up for minutes with heavy disk access, from the discussion
on that feature, it should fix that.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500,
'buildd-unstable'), (500, 'testing'), (100, 'experimental'), (1,
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Bug#875631: linux: [i915/iron lake] Screen flickering instability in 4.9, 4.11 (3.16, 4.12 OK)
Source: linux
Version: 4.9.30-2
Control: fixed -1 3.16.43-2+deb8u2
Control: fixed -1 4.12.6-1
Control: found -1 4.11.6-1
As I mentioned before on IRC, my system with Iron Lake graphics
and a Pentium P6200 (a ThinkPad Edge 15, from 2010 IIRC) is
unstable in stretch. It used to work fine in jessie.
With stretch, the screen flickers, or a horizontal line appears
on the screen, usually when pressing keys (interrupts?). In dmesg
a warning appears:
Sep 11 13:10:43 thinkpad-parents kernel: [drm:ironlake_irq_handler [i915]]
*ERROR* CPU pipe A FIFO underrun
Sep 11 13:10:43 thinkpad-parents kernel: [drm:ironlake_irq_handler [i915]]
*ERROR* PCH transcoder A FIFO underrun
And sometimes the system would just hang.
Tested versions:
* jessie 3.16: stable
* xenial 4.4: still flickers, but does not seem to hang
* stretch 4.9.30: flickers and crashes
* stretch 4.9.47: seems to flicker more
* 4.11.6-1: flickers, not sure if crashes
* 4.12.6-1: no flickering
-- PCI devices:
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series
Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2
Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 5 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express
Root Port 6 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2
Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation HM55 Chipset LPC Interface Controller
(rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port
SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller
(rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series
Chipset Thermal Subsystem (rev 06)
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor
Peak]
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 03)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture
Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture
System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI
Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor
Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor
Reserved (rev 02)
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Bug#827077: linux 4.6: Regression: autofs mounts hang after real mount is unmounted
Package: src:linux
Version: 4.6.1-1
Severity: normal
Hi, my system mounts /boot/efi using autofs, so it is automatically unmounted
after not being used (for safety reasons). The settings are (from /proc/mounts):
systemd-1 /boot/efi autofs
rw,relatime,fd=29,pgrp=1,timeout=10,minproto=5,maxproto=5,direct,pipe_ino=10578
0 0
/dev/sdb1 /boot/efi vfat
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro
0 0
At first, accessing /boot works normally. But once /boot/efi (vfat) is
unmounted, the automount
mount causes processes accessing it to hang (see the dmesg below). Even
manually mounting the vfat
partition does not unhang those processes and new processes still hang.
This affects ls --color /boot for example, which just hangs when doing
lstat("/boot/efi").
This works successfully in 4.5.5-1, and I have not seen the bug in
4.6.0-{rc7,trunk} (but I might
not have looked at /boot in those versions).
-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0
20160603 (Debian 5.4.0-3) ) #1 SMP Debian 4.6.1-1 (2016-06-06)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64
root=UUID=dd840eac-0283-45e9-8f04-ef33f516d29d ro quiet systemd.show_status=1
apparmor=1 security=apparmor
** Tainted: OE (12288)
* Out-of-tree module has been loaded.
* Unsigned module has been loaded (currently expected).
** Kernel log:
[4.269798] input: HDA Intel PCH HDMI/DP,pcm=8 as
/devices/pci:00/:00:1b.0/sound/card0/input16
[4.275694] intel_rapl: Found RAPL domain package
[4.275697] intel_rapl: Found RAPL domain core
[4.275699] intel_rapl: Found RAPL domain uncore
[4.275705] intel_rapl: RAPL package 0 domain package locked by BIOS
[4.302649] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
[4.303033] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input17
[4.303815] [drm] Initialized i915 1.6.0 20160229 for :00:02.0 on minor 0
[4.303942] i801_smbus :00:1f.3: SMBus using PCI interrupt
[4.305470] ACPI Warning: SystemIO range
0x0428-0x042F conflicts with OpRegion
0x0400-0x047F (\_SB.PCI0.LPC.PMIO)
(20160108/utaddress-255)
[4.305476] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[4.305480] ACPI Warning: SystemIO range
0x0540-0x054F conflicts with OpRegion
0x0500-0x057F (\_SB.PCI0.LPC.LPIO)
(20160108/utaddress-255)
[4.305484] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[4.305486] ACPI Warning: SystemIO range
0x0530-0x053F conflicts with OpRegion
0x0500-0x057F (\_SB.PCI0.LPC.LPIO)
(20160108/utaddress-255)
[4.305489] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[4.305491] ACPI Warning: SystemIO range
0x0500-0x052F conflicts with OpRegion
0x0500-0x057F (\_SB.PCI0.LPC.LPIO)
(20160108/utaddress-255)
[4.305494] ACPI: If an ACPI driver is available for this device, you should
use it instead of the native driver
[4.305496] lpc_ich: Resource conflict(s) found affecting gpio_ich
[4.347646] iTCO_vendor_support: vendor-support=0
[4.348068] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[4.348106] iTCO_wdt: Found a Panther Point TCO device (Version=2,
TCOBASE=0x0460)
[4.348256] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[4.495319] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit
banging on pin 5
[4.577475] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts:
commit=600,errors=remount-ro
[4.585040] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts:
commit=600
[4.595887] systemd-journald[341]: Received request to flush runtime journal
from PID 1
[4.604112] usb 1-1.4: USB disconnect, device number 4
[4.649148] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts:
(null)
[4.679194] audit: type=1400 audit(1465687232.141:2): apparmor="STATUS"
operation="profile_load" name="/{usr/,}bin/ping" pid=644 comm="apparmor_parser"
[4.682021] audit: type=1400 audit(1465687232.145:3): apparmor="STATUS"
operation="profile_load" name="gst_plugin_scanner" pid=644
comm="apparmor_parser"
[4.683128] audit: type=1400 audit(1465687232.145:4): apparmor="STATUS"
operation="profile_load" name="klogd" pid=644 comm="apparmor_parser"
[4.684810] audit: type=1400 audit(1465687232.149:5): apparmor="STATUS"
operation="profile_load" name="syslogd" pid=644 comm="apparmor_parser"
[4.686780] audit: type=1400 audit(1465687232.149:6): apparmor="STATUS"
operation="profile_load" name="syslog-ng" pid=644 comm="apparmor_parser"
[4.688765] aud
Bug#827077: linux: autofs mounts hang after real mount is unmounted
Control: found -1 4.5.5-1
Control: retitle -1 linux: autofs mounts hang after real mount is unmounted
On Sun, Jun 12, 2016 at 01:31:34AM +0200, Julian Andres Klode wrote:
> Package: src:linux
> Version: 4.6.1-1
> Severity: normal
>
> Hi, my system mounts /boot/efi using autofs, so it is automatically unmounted
> after not being used (for safety reasons). The settings are (from
> /proc/mounts):
>
> systemd-1 /boot/efi autofs
> rw,relatime,fd=29,pgrp=1,timeout=10,minproto=5,maxproto=5,direct,pipe_ino=10578
> 0 0
> /dev/sdb1 /boot/efi vfat
> rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro
> 0 0
>
> At first, accessing /boot works normally. But once /boot/efi (vfat) is
> unmounted, the automount
> mount causes processes accessing it to hang (see the dmesg below). Even
> manually mounting the vfat
> partition does not unhang those processes and new processes still hang.
>
> This affects ls --color /boot for example, which just hangs when doing
> lstat("/boot/efi").
>
> This works successfully in 4.5.5-1, and I have not seen the bug in
> 4.6.0-{rc7,trunk} (but I might
> not have looked at /boot in those versions).
Hmm, I just reproduced it in 4.5.5-1. Unmounting the autofs thing makes things
work
again. I wonder what's really causing this.
It definitely used to work at some point. Maybe it's actually a systemd issue?
I'm not
exactly sure how autofs works and who actually mounts the vfat and hangs doing
so
(kernel or systemd?).
--
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.
Bug#827077: linux: autofs mounts hang after real mount is unmounted
Control: reassign -1 systemd 230-1
Control: retitle -1 systemd: autofs mount hang in 230
Control: tag -1 patch fixed-upstream
On Mon, Jun 13, 2016 at 12:16:40AM +0200, Julian Andres Klode wrote:
> Control: found -1 4.5.5-1
> Control: retitle -1 linux: autofs mounts hang after real mount is unmounted
>
>
> On Sun, Jun 12, 2016 at 01:31:34AM +0200, Julian Andres Klode wrote:
> > Package: src:linux
> > Version: 4.6.1-1
> > Severity: normal
> >
> > Hi, my system mounts /boot/efi using autofs, so it is automatically
> > unmounted
> > after not being used (for safety reasons). The settings are (from
> > /proc/mounts):
> >
> > systemd-1 /boot/efi autofs
> > rw,relatime,fd=29,pgrp=1,timeout=10,minproto=5,maxproto=5,direct,pipe_ino=10578
> > 0 0
> > /dev/sdb1 /boot/efi vfat
> > rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro
> > 0 0
> >
> > At first, accessing /boot works normally. But once /boot/efi (vfat) is
> > unmounted, the automount
> > mount causes processes accessing it to hang (see the dmesg below). Even
> > manually mounting the vfat
> > partition does not unhang those processes and new processes still hang.
> >
> > This affects ls --color /boot for example, which just hangs when doing
> > lstat("/boot/efi").
> >
> > This works successfully in 4.5.5-1, and I have not seen the bug in
> > 4.6.0-{rc7,trunk} (but I might
> > not have looked at /boot in those versions).
>
> Hmm, I just reproduced it in 4.5.5-1. Unmounting the autofs thing makes
> things work
> again. I wonder what's really causing this.
>
> It definitely used to work at some point. Maybe it's actually a systemd
> issue? I'm not
> exactly sure how autofs works and who actually mounts the vfat and hangs
> doing so
> (kernel or systemd?).
It's a bug in systemd 230. Arch applies the following commit to fix it:
# automount: handle expire_tokens when the mount unit changes its state
(#3434)
0a62f81045dd810c8f1223cccbac4d706ea2cb45
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.
Bug#473430: sendfile support missing in aufs
Laszlo Bako-Szabo wrote:
> Package: aufs-modules-2.6.24-1-amd64
> Severity: important
>
>
> The aufs module no longer has the sendfile capability, the function
> returns with 'Invalid argument' if I try to use it on a aufs filesystem.
> The previous release (2.6.22-3-amd64) works correctly.
>
> Tests were made with lighttpd and a small test program (attached).
aufs has to use splice, but this would need the following patch in the kernel.
Therefore, I think the bug should be reassigned to linux-2.6.
The kernel patch:
Actually, these systemcalls or inode operations were introduced in linux-2.6.17.
But I don't think there exists an application issuces such new systemcalls,
and aufs decided not to support them in linux-2.6.17.
In linux-2.6.23, sendfile inode operation was removed and aufs becomes having to
support splice oprations.
In other words, this patch is for linux-2.6.23 and later. Aufs doesn't support
splice related systemcalls before 2.6.23.
Index: include/linux/splice.h
===
RCS file:
/ext1/sysadm/transparent/repository/linux-2.6.23-rc6/include/linux/splice.h,v
retrieving revision 1.1
retrieving revision 1.3
diff -u -p -r1.1 -r1.3
--- include/linux/splice.h 12 Sep 2007 16:27:22 - 1.1
+++ include/linux/splice.h 14 Sep 2007 03:42:28 - 1.3
@@ -70,4 +70,10 @@ extern ssize_t splice_to_pipe(struct pip
extern ssize_t splice_direct_to_actor(struct file *, struct splice_desc *,
splice_direct_actor *);
+extern long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
+ loff_t *ppos, size_t len, unsigned int flags);
+extern long do_splice_to(struct file *in, loff_t *ppos,
+struct pipe_inode_info *pipe, size_t len,
+unsigned int flags);
+
#endif
Index: fs/splice.c
===
RCS file: /ext1/sysadm/transparent/repository/linux-2.6.23-rc6/fs/splice.c,v
retrieving revision 1.1
retrieving revision 1.3
diff -u -p -r1.1 -r1.3
--- fs/splice.c 12 Sep 2007 16:25:07 - 1.1
+++ fs/splice.c 14 Sep 2007 03:42:27 - 1.3
@@ -943,8 +943,8 @@ EXPORT_SYMBOL(generic_splice_sendpage);
/*
* Attempt to initiate a splice from pipe to file.
*/
-static long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
- loff_t *ppos, size_t len, unsigned int flags)
+long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
+ loff_t *ppos, size_t len, unsigned int flags)
{
int ret;
@@ -964,13 +964,14 @@ static long do_splice_from(struct pipe_i
return out->f_op->splice_write(pipe, out, ppos, len, flags);
}
+EXPORT_SYMBOL(do_splice_from);
/*
* Attempt to initiate a splice from a file to a pipe.
*/
-static long do_splice_to(struct file *in, loff_t *ppos,
-struct pipe_inode_info *pipe, size_t len,
-unsigned int flags)
+long do_splice_to(struct file *in, loff_t *ppos,
+ struct pipe_inode_info *pipe, size_t len,
+ unsigned int flags)
{
int ret;
@@ -990,6 +991,7 @@ static long do_splice_to(struct file *in
return in->f_op->splice_read(in, ppos, pipe, len, flags);
}
+EXPORT_SYMBOL(do_splice_to);
/**
* splice_direct_to_actor - splices data directly between two non-pipes
--
Julian Andres Klode, Fellow of the Free Software Foundation Europe
Debian Maintainer | Developer | Ubuntu Member
try Debian: http://www.debian.org/ | my site: http://jak-linux.org/
jabber: [EMAIL PROTECTED] | IRC: juliank (FreeNode, OFTC)
languages: German | English
signature.asc
Description: OpenPGP digital signature
Bug#480354: sendfile support missing in aufs
On Fri, May 09, 2008 at 05:42:20PM +0300, Laszlo Bako-Szabo wrote:
> Package: linux-image-2.6.24-1-amd64
> Severity: important
>
>
> aufs no longer has the sendfile capability, which seems to be
> because the kernel is missing a patch, that is needed for 2.6.23+ kernels.
> (
> http://aufs.cvs.sourceforge.net/aufs/aufs/patch/splice-2.6.23.patch?view=markup
> )
> The function returns with 'Invalid argument' if I try to use it
> on an aufs filesystem. The last working kernel is 2.6.22-3.
>
> Tests were made with lighttpd and a small test program (attached).
This bug has been fixed already in an upload of aufs (. Please use
module-assistant or wait for the next update of linux-modules-extra-2.6
built against the fixed aufs upload. (-486 and -686 kernels work
already)
>
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers testing
> APT policy: (990, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> /*
> * SENDFILE TEST
> *
> * mkdir -p /tmp/aufs /tmp/aufs1; echo "test" > /tmp/aufs1/test.txt; mount -t
> aufs none /tmp/aufs -o rw,br:/tmp/aufs1
> *
> * ./sendfile-test2 /tmp/aufs/test.txt
> *
> */
>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
> #include
>
> int main(int argc, char **argv)
> {
> int port = 54321, sock_srv, sock_clnt, fd, addrlen;
> struct sockaddr_in addr; off_t offset = 0;
> char buf[1];
>
> if (argc!=2) { printf("Usage: %s \n", argv[0]); }
>
> if ( (sock_srv = socket(AF_INET, SOCK_DGRAM, 0)) == -1) { fprintf(stderr,
> "server socket error: %s\n", strerror(errno)); exit(1); }
> memset(&addr, 0, sizeof(addr)); addr.sin_family = AF_INET;
> addr.sin_addr.s_addr = inet_addr("127.0.0.1"); addr.sin_port = htons(port);
> if ( bind(sock_srv, (struct sockaddr *)&addr, sizeof(addr)) == -1 ) {
> fprintf(stderr, "server bind error: %s\n", strerror(errno)); exit(1); }
>
> if ( (sock_clnt = socket(AF_INET, SOCK_DGRAM, 0)) == -1) { fprintf(stderr,
> "client socket error: %s\n", strerror(errno)); exit(1); }
> if ( connect(sock_clnt, (struct sockaddr *)&addr, sizeof(addr)) == -1 ) {
> fprintf(stderr, "client connect error: %s\n", strerror(errno)); exit(1); }
>
> if ( (fd = open(argv[1], O_RDONLY)) == -1) { fprintf(stderr, "open error:
> %s\n", strerror(errno)); exit(1); }
> offset = 0;
> if ( sendfile (sock_clnt, fd, &offset, 1) == -1) { fprintf(stderr,
> "sendfile error: %s\n", strerror(errno)); exit(1); }
> if ( read(sock_srv, buf, 1) < 1 ) { fprintf(stderr, "read error: %s\n",
> strerror(errno)); exit(1); }
> printf("sendfile seems OK!\n");
> close(fd); close(sock_srv); close(sock_clnt); return 0;
> }
signature.asc
Description: Digital signature
Bug#385553: linux-modules-extra-2.6: ndiswrapper requires rules target override
Daniel Baumann wrote: > Kel Modderman wrote: >> other than >> it not conforming to the standard kbuild invocation as it would if it were >> aiming for mainline Linux exclusion. > > it is a (not yet written) policy that each module-source package needs > to work like this in order get into linux-modules-*. > > why/what is it so difficult to add/adjust the toplevel makefile to do that? Fixed locally. I will publish the new package soon and it should be uploaded soon. Using the patch from https://bugs.edge.launchpad.net/ndiswrapper/+bug/241547 > -- Julian Andres Klode, Fellow of the Free Software Foundation Europe Debian Maintainer | Developer | Ubuntu Member try Debian: http://www.debian.org/ | my site: http://jak-linux.org/ jabber: [EMAIL PROTECTED] | IRC: juliank (FreeNode, OFTC) languages: German | English signature.asc Description: OpenPGP digital signature
Bug#385553: linux-modules-extra-2.6: Please provide pre-built ndiswrapper modules
Daniel Baumann wrote: > Any progress on ndiswrapper? > Kel Modderman wrote: > Vcs-Svn and Julian was planning to have an upload sponsored soon. I guess > he has been busy, I've just been patiently waiting for the transfer to occur. > > Julian, please let us know how we should proceed, we should get upstream > version 1.53 in the archive ASAP. Sorry, I wasn't at home in the last 2 weeks. Should get uploaded this week. I will do some final builds and tests and see if my AM sponsors it, else I will look for another sponsor. ETA: 3d (maximum) -- Julian Andres Klode, Fellow of the Free Software Foundation Europe Debian Maintainer | Developer | Ubuntu Member try Debian: http://www.debian.org/ | my site: http://jak-linux.org/ jabber: [EMAIL PROTECTED] | IRC: juliank (FreeNode, OFTC) languages: German | English signature.asc Description: OpenPGP digital signature
Bug#533550: i915: kernel mode setting -- wrong resolution
linux-image-2.6.30-1-amd64/preinst/elilo-initrd-2.6.30-1-amd64: true linux-image-2.6.30-1-amd64/preinst/bootloader-initrd-2.6.30-1-amd64: true linux-image-2.6.30-1-amd64/preinst/overwriting-modules-2.6.30-1-amd64: true linux-image-2.6.30-1-amd64/postinst/depmod-error-2.6.30-1-amd64: false linux-image-2.6.30-1-amd64/preinst/failed-to-move-modules-2.6.30-1-amd64: linux-image-2.6.30-1-amd64/postinst/depmod-error-initrd-2.6.30-1-amd64: false linux-image-2.6.30-1-amd64/preinst/abort-install-2.6.30-1-amd64: linux-image-2.6.30-1-amd64/postinst/bootloader-test-error-2.6.30-1-amd64: linux-image-2.6.30-1-amd64/postinst/old-system-map-link-2.6.30-1-amd64: true -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ signature.asc Description: Digital signature
Bug#533550: i915: kernel mode setting -- wrong resolution
On Fri, Jun 19, 2009 at 01:35:56PM +0200, Julien Cristau wrote: > On Thu, Jun 18, 2009 at 17:55:17 +0200, Julian Andres Klode wrote: > > > > [1.793657] [drm] TV-13: set mode 1024x768 18 > > > Is a TV really connected? If not this should be fixed with: I don't even have a TV output, so none can be connected. > commit 03d6069912babc07a3da20e715dd6a5dc8f0f867 > Author: Keith Packard > Date: Fri Jun 5 18:19:56 2009 -0700 > > drm/i915: Hook connector to encoder during load detection (fixes tv/vga > detect > > With the DRM-driven DPMS code, encoders are considered idle unless a > connector is hooked to them, so mode setting is skipped. This makes load > detection fail as none of the hardware is enabled. > > Signed-off-by: Keith Packard > Signed-off-by: Eric Anholt -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553472: linux-libc-dev: Include linux/aufs_type.h for aufs2-utils?
Package: linux-libc-dev Version: 2.6.31-1 Severity: wishlist Hi, would it be possible to get linux/aufs_type.h included in linux-libc-dev or a similar package? This header is needed to build the userspace tools of aufs, which include programs such as mount.aufs or auchk. Currently it is included in linux-headers-2.6.31-common but this package is versioned and would thus require changes to aufs-tools build-dependencies for every new kernel. Regards, Julian -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#553472: linux-libc-dev: Include linux/aufs_type.h for aufs2-utils?
Am Samstag, den 31.10.2009, 18:42 + schrieb Ben Hutchings: > On Sat, 2009-10-31 at 17:50 +0100, Julian Andres Klode wrote: > > Package: linux-libc-dev > > Version: 2.6.31-1 > > Severity: wishlist > > > > Hi, would it be possible to get linux/aufs_type.h included in > > linux-libc-dev or a similar package? This header is needed to > > build the userspace tools of aufs, which include programs such > > as mount.aufs or auchk. > > > > Currently it is included in linux-headers-2.6.31-common but > > this package is versioned and would thus require changes to > > aufs-tools build-dependencies for every new kernel. > > Is this a stable ABI? The last ABI break was on Aug 23; and it's only used by aufs-tools. The idea of including it in linux-libc-dev just seems better than all other options. So I don't know how stable the ABI really is, but I have only seen 2 ABI breaks since March. I could also include the header file into the aufs-tools source package like btrfs-tools does but I just think it's better to include it here, especially considering Debian derivatives. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567391: Please update aufs2 to new upstream snapshot (aufs2-32 branch)
Package: linux-2.6 Version: 2.6.32-5 Severity: wishlist Hi, please update aufs2 to a newer upstream code. The latest upstream release (i.e. git push) was on Jan 25 and the next one is expected for Feb 2 (next monday). Regards, Julian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. signature.asc Description: Digital signature
Bug#567965: i915: KMS framebuffer fails to work, only X works
ce [103c:30d8] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3) (prog-if 01 [Subtractive decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:30d8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03) (prog-if 8a [Master SecP PriP]) Subsystem: Hewlett-Packard Company Device [103c:30d8] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Kernel driver in use: ahci 10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02) Subsystem: Hewlett-Packard Company Compaq 6710b or nx9420 Notebook [103c:135c] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwl3945 ** USB devices: Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-trunk-amd64 depends on: ii debconf [debconf-2.0]1.5.28 Debian configuration management sy ii initramfs-tools [linux-initr 0.93.4 tools for generating an initramfs ii module-init-tools3.12~pre1-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-trunk-amd64 recommends: ii firmware-linux-free 2.6.32-5 Binary firmware for various driver Versions of packages linux-image-2.6.32-trunk-amd64 suggests: pn grub | lilo(no description available) pn linux-doc-2.6.32 (no description available) Versions of packages linux-image-2.6.32-trunk-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.22 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink(no description available) -- debconf information: linux-image-2.6.32-trunk-amd64/postinst/bootloader-error-2.6.32-trunk-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.32-trunk-amd64/postinst/depmod-error-initrd-2.6.32-trunk-amd64: false linux-image-2.6.32-trunk-amd64/prerm/removing-running-kernel-2.6.32-trunk-amd64: true linux-image-2.6.32-trunk-amd64/postinst/bootloader-test-error-2.6.32-trunk-amd64: linux-image-2.6.32-trunk-amd64/postinst/missing-firmware-2.6.32-trunk-amd64: linux-image-2.6.32-trunk-amd64/prerm/would-invalidate-boot-loader-2.6.32-trunk-amd64: true -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. signature.asc Description: Digital signature
Bug#567965: linux-image-2.6.32-trunk-686: Configuration change to prevent i915 lockup
found 567965 2.6.32-6 thanks On Tue, Feb 02, 2010 at 10:43:59PM +, Ben Hutchings wrote: > On Tue, 2010-02-02 at 17:12 -0500, Matthew James Goins wrote: > > Package: linux-2.6 > > Version: 2.6.32-5 > > Severity: normal > > Please test 2.6.32-6 which is in unstable now. > Instead of Matthew, I tested it (as the submitter), and it still happens. The thing is caused by grub not leaving the graphics mode and the kernel drivers unable to set a new mode. You may also want to take a look at grub-pc's Bug#565160. Regards, Julian -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. signature.asc Description: Digital signature
Re: Bug#520468: Incorporate fixes for WUSB54GS support from 2.6.33
reassign 520468 linux-2.6 severity 520468 normal retitle 520468 Incorporate fixes for WUSB54GS support from 2.6.33 thanks Am Samstag, den 06.02.2010, 17:00 + schrieb Luís Picciochi Oliveira: > Hello, > I just tested ndiswrapper 1.55. It is still giving the same output as > before. > > However, I have been using linux kernel 2.6.33-rc1 because this card > is now supported and works well on it. So, I don't need ndiswrapper > anymore. > Notice that with 2.6.32 (currently at the testing repositories) this > card is detected by the kernel but there are some problems with the > module that were only resolved with 2.6.33, so people using it might > still need to resort to ndiswrapper. > > Regards, > Pitxyoki I am reassigning this bug to linux-2.6 with the request to incorporate fixes for the issues in wusb54gs support into the native module; as I do not support ndiswrapper for cards which have native drivers in mainline. Regards, Julian -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1266398935.2729.3.ca...@hp
Bug#572341: Use of uninitialized value $type in exists at /var/lib/dpkg/info/linux-base.postinst line 1271, line 4.
Package: linux-2.6 Version: 2.6.33-1~experimental.2 When installing kernel 2.6.33, I get Use of uninitialized value $type in exists at /var/lib/dpkg/info/linux-base.postinst line 1271, line 4. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.33-2-amd64 depends on: ii debconf [debconf 1.5.28 Debian configuration management sy ii initramfs-tools 0.93.4 tools for generating an initramfs ii linux-base 2.6.33-1~experimental.2 Linux image base package ii module-init-tool 3.12~pre1-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.33-2-amd64 recommends: ii firmware-linux-free 2.6.32-9 Binary firmware for various driver Versions of packages linux-image-2.6.33-2-amd64 suggests: pn grub | lilo(no description available) pn linux-doc-2.6.33 (no description available) Versions of packages linux-image-2.6.33-2-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.22 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink(no description available) -- debconf-show failed -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpPtm3EiS5ZI.pgp Description: PGP signature
Bug#591768: linux-2.6: rmdir: failed to remove `/lib/modules/2.6.35-rc6-amd64': Directory not empty
Package: linux-2.6 Severity: normal When I uninstall kernels, I get warnings like: rmdir: failed to remove `/lib/modules/2.6.32-3-amd64': Directory not empty rmdir: failed to remove `/lib/modules/2.6.35-rc6-amd64': Directory not empty The reason is a file named 'modules.devname' in those directories. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf 1.5.33 Debian configuration management sy ii initramfs-tools 0.97.2 tools for generating an initramfs ii linux-base 2.6.35-1~experimental.1 Linux image base package ii module-init-tool 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: pn firmware-linux-free(no description available) Versions of packages linux-image-2.6.32-5-amd64 suggests: pn grub | lilo(no description available) pn linux-doc-2.6.32 (no description available) Versions of packages linux-image-2.6.32-5-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.26 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink(no description available) pn xen-hypervisor (no description available) -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgp0Uh2kosKHA.pgp Description: PGP signature
Bug#591777: linux-2.6: Large vaapi performance drop from 2.6.35-rc6 to 2.6.35
400 Series Chipset SMBus Controller [8086:3b30] (rev 06) Subsystem: Lenovo Device [17aa:2167] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- 03:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 1000 [8086:0084] Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN [8086:1315] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlagn 09:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03) Subsystem: Lenovo Device [17aa:2131] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: r8169 ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02) Subsystem: Lenovo Device [17aa:2196] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- (no description available) Versions of packages linux-image-2.6.35-trunk-amd64 suggests: pn grub | lilo(no description available) pn linux-doc-2.6.35 (no description available) Versions of packages linux-image-2.6.35-trunk-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.26 Binary firmware for Intel Wireless pn firmware-linux (no description available) pn firmware-linux-nonfree (no description available) pn firmware-qlogic(no description available) pn firmware-ralink (no description available) pn xen-hypervisor (no description available) -- debconf information excluded -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgprCQZcAy5iz.pgp Description: PGP signature
Bug#579755: linux-2.6: Please enable CONFIG_CGROUP_DEBUG
Package: linux-2.6 Severity: wishlist Hi, it would be useful to have CONFIG_CGROUP_DEBUG enabled. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. pgpwJDzVVNgFj.pgp Description: PGP signature
unification filesystems -- packaging aufs2, etc.
Hi everyone,
I would like to remove aufs from Debian soon, as it is not maintained
upstream anymore. But before this can happen, we have to find an
alternative which provides a reasonable feature set and comparable
performance.
This email is sent to the debian-kernel team for advice on the
kernel-based solutions and to the debian-live team as the most
important user. I also CCed the maintainers of the userspace
filesystems.
Why remove aufs1?
-
The last update to aufs1 is from January 2009. It has since been
replaced by aufs2. I don't want to maintain a whole filesystem
without any kind of upstream.
Alternatives: Kernelspace filesystems
-
There are two candidates: Unionfs2 and Aufs2. The problem with both
filesystems is that they require patches to the kernel, whereas aufs2
seems to be safer as it requires only new exports to be added.
There is also a new technology called union-mount, but I don't know
how mature this solution is.
None of these filesystems are packaged yet. If we were to decide for
kernel-based unification, one of those has to be packaged and the
kernel team has to accept patches to make this work.
I have attached the kernel patches needed for each filesystem, so
they can be reviewed. The Unionfs patch can be reduced to export
do_splice_{from,to} (without renaming to vfs_splice_{from,to}),
exporting security_inode_permission and the change to
fsstack_copy_inode_size(). The aufs patch is larger, but has the
benefit of only adding new exports without changing existing
functions.
Alternatives: Userspace filesystems
---
There are also userspace alternatives. Debian currently provides
unionfs-fuse, packaged by Bernd Schubert .
Another alternative seems to be mhddfs, packaged by
Dmitry E. Oboukhov .
Proposal
-
It seems to be the best idea to use unionfs-fuse for now (like Ubuntu)
until a new kernel-based solution has been packaged. It may also be a
good idea to coordinate this with the Ubuntu developers, so both distros
can use the same method of filesystem unification.
1. The Debian Live project adds support for unionfs-fuse.
2. A new filesystem will be packaged (unionfs2 OR aufs2).
3. aufs will be removed from unstable (or be replaced by
aufs2 under the same name).
Regards,
Julian Andres Klode
(Please always CC me on replies, I'm not subscribed to any of the
mailing lists this mail is sent to.)
--
Julian Andres Klode - Free Software Developer
Debian Developer - Contributing Member of SPI
Ubuntu Member - Fellow of FSFE
Website: http://jak-linux.org/ XMPP: juli...@jabber.org
Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/
Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/
aufs2 standalone patch for linux-2.6.30
diff --git a/fs/namei.c b/fs/namei.c
index 967c3db..64a5060 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -337,6 +337,7 @@ int deny_write_access(struct file * file)
return 0;
}
+EXPORT_SYMBOL(deny_write_access);
/**
* path_get - get a reference to a path
@@ -1200,7 +1201,7 @@ out:
* needs parent already locked. Doesn't follow mounts.
* SMP-safe.
*/
-static struct dentry *lookup_hash(struct nameidata *nd)
+struct dentry *lookup_hash(struct nameidata *nd)
{
int err;
@@ -1209,8 +1210,9 @@ static struct dentry *lookup_hash(struct nameidata *nd)
return ERR_PTR(err);
return __lookup_hash(&nd->last, nd->path.dentry, nd);
}
+EXPORT_SYMBOL(lookup_hash);
-static int __lookup_one_len(const char *name, struct qstr *this,
+int __lookup_one_len(const char *name, struct qstr *this,
struct dentry *base, int len)
{
unsigned long hash;
@@ -1231,6 +1233,7 @@ static int __lookup_one_len(const char *name, struct qstr *this,
this->hash = end_name_hash(hash);
return 0;
}
+EXPORT_SYMBOL(__lookup_one_len);
/**
* lookup_one_len - filesystem helper to lookup single pathname component
diff --git a/fs/namespace.c b/fs/namespace.c
index 134d494..5a6d038 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -38,6 +38,7 @@
/* spinlock for vfsmount related operations, inplace of dcache_lock */
__cacheline_aligned_in_smp DEFINE_SPINLOCK(vfsmount_lock);
+EXPORT_SYMBOL(vfsmount_lock);
static int event;
static DEFINE_IDA(mnt_id_ida);
diff --git a/fs/open.c b/fs/open.c
index bdfbf03..81c39b3 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -221,6 +221,7 @@ int do_truncate(struct dentry *dentry, loff_t length, unsigned int time_attrs,
mutex_unlock(&dentry->d_inode->i_mutex);
return err;
}
+EXPORT_SYMBOL(do_truncate);
static long do_sys_truncate(const char __user *pathname, loff_t length)
{
diff --git a/fs/splice.c b/fs/splice.c
index 666953d..fbc3f77 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -905,8 +905,8 @@ EXPORT_SYMBOL(generic_splice_sendpage);
/*
* Attempt to initiate a splice from pipe to file.
*/
-static long do_splice_from(struct pipe_inode_info *pipe, struct file *out
Bug#535959: linux-2.6: Please enable libata for PATA/piix
On Mon, Jul 06, 2009 at 01:02:54PM +0200, Michael Biebl wrote: > Package: linux-2.6 > Severity: normal > > Hi, > > currently the Debian linux package explicitly disables libata for > ata_piix via > debian/patches/debian/drivers-ata-ata_piix-postpone-pata.patch. > which means that the old IDE subsystem is used for this chipset. > I'd like to see this patch removed, so libata is used by default. I would like to see this as well. Most other distributions have already switched to the new system and it's a bit silly to have two subystems loaded on a modern laptop when both devices (SATA HDD, PATA DVD) can be supported by just one subsystem (it reduces the amount of code running on the system). -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: unification filesystems -- packaging aufs2, etc.
On Mon, Jul 6, 2009 at 6:10 PM, Daniel Baumann wrote: > in the meanwhile, having not looked at the issues myself at all, is it > reasonably possible to patch aufs1 for 2.6.30? I have already compiled it against 2.6.30 using the current version in unstable, but I have not tested the module yet. It should work. -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: unification filesystems -- packaging aufs2, etc.
On Mon, Jul 06, 2009 at 06:10:32PM +0200, Daniel Baumann wrote: > Julian Andres Klode wrote: > > Proposal > > - > > It seems to be the best idea to use unionfs-fuse for now (like Ubuntu) > > until a new kernel-based solution has been packaged. It may also be a > > good idea to coordinate this with the Ubuntu developers, so both distros > > can use the same method of filesystem unification. > > > > 1. The Debian Live project adds support for unionfs-fuse. > > this shouldn't be that hard, however, it's a serious regression in terms > of speed, therefore i really hope kernel team will accepts aufs2 patches. Another option for Debian Live would be to use Device Mapper, like Fedora does, by using an ext3 image which is located inside a SquashFS image. This way, you only need functionality already provided by the kernel and no external modules. But even if this is a realistic option, we still need filesystems such as unionfs or aufs for other users. And hacking the filesystem to work without kernel patches is possible, but it leads to security problems and probably other problems as well. -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ signature.asc Description: Digital signature
Bug#541828: linux-2.6: Please export symbols for aufs2 (or unionfs2).
Package: linux-2.6
Severity: wishlist
Tags: patch
Currently, we are shipping aufs1 in Debian unstable, which is
not supported upstream anymore since January 2009. This is a
bad situation.
We now have 3 options:
1) Ship aufs2 (which requires 18 symbol exports in the kernel)
2) Ship unionfs2 (which requires 4 symbol exports in the kernel)
3) Ship no kernel-based union filesystem
Option 1 (aufs2):
The straight-forward way from aufs would be to migrate to
aufs2. This option has been chosen by projects like Ubuntu
and is preferred by the Debian Live team.
In comparison to unionfs2, aufs2 has several disadvantages;
it is much larger and thus harder to maintain, it requires
many more exports.
Choosing this option would also allow us to implement option
2 at the same time, as aufs2's symbol export patch is basically
a superset of unionfs2's one.
Option 2 (unionfs2):
UnionFS has been dropped from Debian in the past, because its
maintainer favoured aufs1. The benefit of aufs1 is the much
smaller codebase, the small number of to-be-exported symbols.
Option 3 (not kernel-based, performance ISSUES):
This option may have a large negative impact on the performance
of Debian Live and is not acceptable for them. It was used by
Ubuntu for a short time during their 'karmic' alpha cycle, but
replaced by aufs2.
All in all, I would like you to apply the attached patch
(aufs2-standalone.diff) to the kernel, so we can continue with
option 1. If you think that this option is not acceptable, please
apply unionfs.diff so we can implement option 2.
We could get Unionfs working without any kernel patches at all,
but it would certainly cause security problems, like ignored
file permissions.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
aufs2 standalone patch for linux-2.6.30
diff --git a/fs/namei.c b/fs/namei.c
index 967c3db..64a5060 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -337,6 +337,7 @@ int deny_write_access(struct file * file)
return 0;
}
+EXPORT_SYMBOL(deny_write_access);
/**
* path_get - get a reference to a path
@@ -1200,7 +1201,7 @@ out:
* needs parent already locked. Doesn't follow mounts.
* SMP-safe.
*/
-static struct dentry *lookup_hash(struct nameidata *nd)
+struct dentry *lookup_hash(struct nameidata *nd)
{
int err;
@@ -1209,8 +1210,9 @@ static struct dentry *lookup_hash(struct nameidata *nd)
return ERR_PTR(err);
return __lookup_hash(&nd->last, nd->path.dentry, nd);
}
+EXPORT_SYMBOL(lookup_hash);
-static int __lookup_one_len(const char *name, struct qstr *this,
+int __lookup_one_len(const char *name, struct qstr *this,
struct dentry *base, int len)
{
unsigned long hash;
@@ -1231,6 +1233,7 @@ static int __lookup_one_len(const char *name, struct qstr *this,
this->hash = end_name_hash(hash);
return 0;
}
+EXPORT_SYMBOL(__lookup_one_len);
/**
* lookup_one_len - filesystem helper to lookup single pathname component
diff --git a/fs/namespace.c b/fs/namespace.c
index 134d494..5a6d038 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -38,6 +38,7 @@
/* spinlock for vfsmount related operations, inplace of dcache_lock */
__cacheline_aligned_in_smp DEFINE_SPINLOCK(vfsmount_lock);
+EXPORT_SYMBOL(vfsmount_lock);
static int event;
static DEFINE_IDA(mnt_id_ida);
diff --git a/fs/open.c b/fs/open.c
index bdfbf03..81c39b3 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -221,6 +221,7 @@ int do_truncate(struct dentry *dentry, loff_t length, unsigned int time_attrs,
mutex_unlock(&dentry->d_inode->i_mutex);
return err;
}
+EXPORT_SYMBOL(do_truncate);
static long do_sys_truncate(const char __user *pathname, loff_t length)
{
diff --git a/fs/splice.c b/fs/splice.c
index 666953d..fbc3f77 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -905,8 +905,8 @@ EXPORT_SYMBOL(generic_splice_sendpage);
/*
* Attempt to initiate a splice from pipe to file.
*/
-static long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
- loff_t *ppos, size_t len, unsigned int flags)
+long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
+ loff_t *ppos, size_t len, unsigned int flags)
{
int ret;
@@ -925,13 +925,14 @@ static long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
return out->f_op->splice_write(pipe, out, ppos, len, flags);
}
+EXPORT_SYMBOL(do_splice_from);
/*
* Attempt to initiate a splice from a file to a pipe.
*/
-static long do_splice_to(struct file *in, loff_t *ppos,
- struct pipe_inode_info *pipe, size_t len,
- unsigned int flags)
+lo
