October 2013 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel-default-base-2.6.29-5.2.x86_64 rpm errors
by Dave Plater 18 Jul '24

18 Jul '24

Hi, I'm busy updating to the latest factory kernel and have received the following errors from kernel-default-base installation (I did insert a blank dvd during the installation of the rpm by zypper):- WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol register_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_ioctl WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_media_changed WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_get_media_event WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_release WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_open WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol unregister_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_number_of_slots And then these errors which I think IIRC happened before when the kernel was first split into three:- Kernel image: /boot/vmlinuz-2.6.29-rc8-5-default Initrd image: /boot/initrd-2.6.29-rc8-5-default Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part3 (/dev/sda3) (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part2 (/dev/sda2) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module xfs not found. WARNING: no dependencies for kernel module 'xfs' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: scsi_mod libata ata_piix edd ahci sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd WARNING: /dev/shm/mkinitramfs.0drQsZ/mnt/lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 22669 blocks Should I open a bug report about the errors which are possibly from inserting a dvd while the kernel rpm was installing? Regards Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] Modular drivers which could be built-in
by Jean Delvare 10 Mar '14

10 Mar '14

Hi all, Having worked on built-in drivers which could be modularized, I am now looking for modular drivers which could be built-in. Our policy is that drivers which are not hardware-specific and are needed on a majority of systems should be built into the kernel directly. So I checked which modules were loaded on my 4 systems. After filtering out hardware-specific modules, I am left with the following list: ACPI and thermal drivers: * button * processor * thermal_sys Block device drivers * cdrom * scsi_dh * scsi_dh_alua * scsi_dh_emc * scsi_dh_hp_sw * scsi_dh_rdac * sg * sr_mod Graphics helper drivers * drm * drm_kms_helper * i2c_algo_bit Filesystem drivers: * fuse * lockd * sunrpc CPU drivers: * microcode Sound drivers: * pcspkr * snd * snd_page_alloc * snd_pcm * snd_seq * snd_seq_device * snd_timer * soundcore If anyone has an opinion on whether these should be built into the kernel or left as modules, this is the right time to discuss it. My personal thoughts, with mostly x86 in mind: * The ACPI button and processor drivers could be built-in. Most x86 systems use ACPI and they supposedly all have at least one processor and one power button ;) And thermal_sys is selected by processor. * While all my systems have an optical drive, I know they have disappeared from many systems, both very small and very large ones, so leaving cdrom and sr_mod as modules seems fine. * I have no idea why/how sg is being loaded, it has no modalias and no other module depend on it. But /dev/sd* nodes are created so it is certainly useful. Hannes? * No idea what the scsi_dh* modules are about either, no modalias and no dependencies either. Hannes? * With DRM/KMS being the norm now, I believe drm and drm_kms_helper could be built-in, even though the former is quite large. drm selects i2c-algo-bit, most (all?) DRM/KMS drivers use it. Even servers have graphics chips. * I suppose fuse is only used on desktop machines by default, for gvfs, so having it as a module seems OK. * lockd and sunrpc are dependencies of nfs and nfsd. I suppose there are many users out there who don't serve nor mount NFS shares so modules make sense. * I think microcode could be unloaded after use, maybe for security reasons it might even be preferable, or just because there is simply no point in keeping it in memory. Thomas? Either way we should keep it modular. * For sound drivers, Takashi should know better than me. I suppose that the rationale for having these modular is that servers have no sound chip? -- Jean Delvare Suse L3 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

15 61

[opensuse-kernel] CONFIG_CC_STACKPROTECTOR
by richard -rw- weinberger 14 Dec '13

14 Dec '13

Hi! I'm wondering why CONFIG_CC_STACKPROTECTOR is disabled on openSUSE. Debian and Fedora seem to enabled it per default. What's the deal? -- Thanks, //richard -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 17

[opensuse-kernel] pcieport 0000:00:03.0: driver skip pci_set_master, fix it!
by Cristian Rodríguez 08 Dec '13

08 Dec '13

I am getting the message in $SUBJECT with current kernel:HEAD lspci said that device is: 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 13) No idea how to proceed further or if this something to be concerned. Any hint appreciated. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 5

[opensuse-kernel] openSUSE 13.1+ kernel config
by Jean Delvare 08 Nov '13

08 Nov '13

Hi all, I was looking at the openSUSE 13.1 kernel config and noticed the following settings which I'd like to discuss. # CONFIG_BATMAN_ADV_NC is not set Given that all other CONFIG_BATMAN_ADV_* options are enabled, what is the rationale for not enabling CONFIG_BATMAN_ADV_NC too? I'm not using Batman so I don't care personally, but for consistency it seems this option should be enabled. # CONFIG_GPIO_SCH is not set # CONFIG_GPIO_PCH is not set These were disabled on purpose by commit f554d8b2: Author: Jeff Mahoney <jeffm(a)suse.com> Date: Sun May 13 22:31:50 2012 -0400 Disabled more Intel embedded drivers. Disabled: - CONFIG_GPIO_LANGWELL - CONFIG_GPIO_PCH - CONFIG_GPIO_SCH But meanwhile (kernel v3.5) the gpio-sch driver was added support for the Intel Centerton microprocessor family, which I'm fairly sure we want to fully support. I am also wondering about gpio-pch because it supports a chipset for Tunnel Creek (Intel Atom E6xx) processors since kernel v3.3, and I don't quite understand why we wouldn't want to support these. I seem to recall it was already discussed but I can no longer find the discussion so I can't verify. But I see we have CONFIG_PCH_PHUB=m, CONFIG_PCH_GBE=m and CONFIG_PCH_DMA=m, so CONFIG_GPIO_PCH=m would seem consistent. # CONFIG_INTEL_POWERCLAMP While I don't expect this driver to get widely used, it could be useful in specific cases, like machines working in extreme conditions, temporary workaround to fan or air conditioning system failure, or debugging. The driver is small and unintrusive, so I see no downside to including it. -- Jean Delvare Suse L3 Support -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] Re: aacraid driver crash when it shouldn't
by Bruno Friedmann 05 Nov '13

05 Nov '13

Thanks for asking information I provide attached a tar.bz2 with all the information I can grab from the computer in the hope you will be able to reproduce. A backup link is at https://dl.dropboxusercontent.com/u/13333867/clochette.support-logs.tar.bz2 (The controler has been showing the same kind of error with another motherboard AMD X6 1090 based) The way to reproduce exactly is a bit conplicated : On the controleur we have 8 intel 510 (same firmware) normally in the supported device adaptec list assembled in a RAID6 with 1Mb chunksize. on the operating system : pure openSUSE 12.3 x86_64 we have defined a logical volume containing the whole raid (sde) on this one we have 2 lv (~250GB each) which are used as primary disk for the 2 virtual machines The you get a 3.7.10 kernel. We try to use the latest kernel available this week-end 3.11.0-2.g0a1c41f-default. A new 3.11.1 was published since but we don't yet upgrade to it. We use qemu-kvm virtualisation and setup 2 vms ( Windows 2008-R2 64bits ) with virtio drivers 0.1.5.2 stable from fedora installed to support para-virt for disk and network. The vm are started with the following definition qemu 5285 18.9 25.0 13160744 8210400 ? Sl 07:28 7:33 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name peterpan -S -machine pc-0.15,accel=kvm,usb=off -cpu Westmere,+erms,+smep,+fsgsbase,+rdtscp,+rdrand,+f16c,+avx,+osxsave,+xsave,+tsc-deadline,+pcid,+pdcm,+xtpr,+tm2,+est,+vmx,+ds_cpl,+monitor,+dtes64,+pclmuldq,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid bdc39043-721b-4bcd-9580-ff5a942f63c6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/peterpan.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vgvms/lvpeterpan_2008,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -drive file=/var/lib/libvirt/images/virtio-win-0.1-52.iso,if=none,id=drive-ide0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=22 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:f0:d3:74,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -device vmware-svga,id=video0,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x6 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 What we have discovered saturday is the following, if we put disk cache to writethrought and run oracle dumps (exp) then the crash will occur more than with cache=none. With cache=none the vm and host have run during 3 days without big incident but finally die during this night. What I can tell more is that the same hardware : controler and ssd disk with firmware 19076 have run during years without any trouble with a kernel 3.1.10 (was openSUSE 12.1) On Tuesday 17 September 2013 23.27:54 Mahesh Rajashekhara wrote: > Hi, > > > > Author: Mahesh Rajashekhara <Mahesh.Rajashekhara@XXXXX> > > Date: Tue Jun 18 17:02:07 2013 +0530 > > > > SCSI: aacraid: Fix for arrays are going offline in the system. System hangs > > > > commit c5bebd829dd95602c15f8da8cc50fa938b5e0254 upstream. > > > > This driver patch has a fix for race condition between the doorbell and the circular buffer. This one fixes SCSI command timeout issue with Sync. mode driver. I understand, you were using Series 6 and the in-box driver switches to Async mode by default. So, this patch has no effect. > > > > I have tried to duplicate this issue. But, I cannot reproduce this issue yet. > > > > Can you please send us the detailed steps for reproducing this issue ? > > OS ? > > Kernel source download link ? > > IO tool? > > > > Also, can you please obtain the support archive from the controller after reboot (after the issue happened)? > > > > The syntax is: > > > > arcconf savesupportarchive > > > > This stores all the logs into log folder (you will see the path where it is stored in the response) and please provide all the files in that folder. > > > > Thanks, > > Mahesh > > -----Original Message----- > From: Bruno Friedmann [mailto:bruno@ioda-net.ch] > Sent: Sunday, September 15, 2013 3:20 PM > To: opensuse-kernel(a)opensuse.org > Cc: Mahesh Rajashekhara > Subject: aacraid driver crash when it shouldn't > > > > Hi there, I'm facing an issue with 3.11 coming from our kernel-stable repos > > > > A intel motherboard + i7 3770 32Gb ram with an adaptec 6805 adapter. > > (8 intel ssd 510 series 120 go attached in a raid6 array) > > > > The bundle adaptec + ssd in raid6 has worked during months (with openSUSE 12.1) without any glitches. > > > > Now this night we received that kind of error > > > > Sep 15 02:06:52 clochette.disney.interne kernel: aacraid: Host adapter abort request (6,0,0,0) Sep 15 02:06:52 clochette.disney.interne kernel: aacraid: Host adapter abort request (6,0,0,0) Sep 15 02:06:52 clochette.disney.interne kernel: aacraid: Host adapter reset request. SCSI hang ? > > Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] Medium access timeout failure. Offlining disk! > > Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: Device offlined - not ready after error recovery Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: Device offlined - not ready after error recovery Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] Unhandled error code Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] Sep 15 02:07:07 clochette.disney.interne kernel: Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] CDB: > > Sep 15 02:07:07 clochette.disney.interne kernel: Write(10): 2a 00 02 b7 f4 00 00 00 20 00 Sep 15 02:07:07 clochette.disney.interne kernel: end_request: I/O error, dev sde, sector 45609984 Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-4, logical block 5252224 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-4 Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-4, logical block 5252225 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-4 Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-4, logical block 5252226 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-4 Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-4, logical block 5252227 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-4 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] Unhandled error code Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] Sep 15 02:07:07 clochette.disney.interne kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: [sde] CDB: > > Sep 15 02:07:07 clochette.disney.interne kernel: Write(10): 2a 00 31 3e f6 20 00 00 08 00 Sep 15 02:07:07 clochette.disney.interne kernel: end_request: I/O error, dev sde, sector 826209824 Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 853188 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-3 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 2981929 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 2981929 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 45451 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-3 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 785908 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-3 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device Sep 15 02:07:07 clochette.disney.interne kernel: Buffer I/O error on device dm-3, logical block 810442 Sep 15 02:07:07 clochette.disney.interne kernel: lost page write due to I/O error on dm-3 Sep 15 02:07:07 clochette.disney.interne kernel: sd 6:0:0:0: rejecting I/O to offline device > > > > > > But after checking kernel changelog I've found this commit for 3.10 series which should have fix it? > > > > > > Author: Mahesh Rajashekhara <Mahesh.Rajashekhara@XXXXX <mailto:Mahesh.Rajashekhara@XXXXX> > > > Date: Tue Jun 18 17:02:07 2013 +0530 > > > > SCSI: aacraid: Fix for arrays are going offline in the system. System hangs > > > > commit c5bebd829dd95602c15f8da8cc50fa938b5e0254 upstream. > > > > One of the customer had reported that the set of raid logical arrays will > > become unavailable (I/O offline) after a long hours of IO stress test. The OS > > wouldn`t be accessible afterwards and require a hard reset. > > > > This driver patch has a fix for race condition between the doorbell and the > > circular buffer. The driver is modified to do an extra read after clearing the > > doorbell in case there had been a completion posted during the small timing > > window. > > > > With this fix, we ran IO stress for ~13 days. There were no IO failures. > > > > Signed-off-by: Mahesh Rajashekhara <Mahesh.Rajashekhara@XXXX <mailto:Mahesh.Rajashekhara@XXXX> > > > Signed-off-by: James Bottomley <JBottomley@XXXX> > > Signed-off-by: Greg Kroah-Hartman <gregkh@XXXXX> > > > > > > Then it's hard to find what's going wrong ? > > > > Should the firmware being downgraded to previous rev 19076 as it was before the mainboard change and openSUSE 12.3 installation ? > > > > On this Raid6 we have a LVM group which contain virtuals machines who were running with a consequent load (oracle dumps) > > running from 1.5 to 2 hours. > > > > Thanks for any pointer, or feedback > > I can provide more information if needed. > > > > > > -- > > > > Bruno Friedmann > > Ioda-Net Sàrl www.ioda-net.ch <http://www.ioda-net.ch> > > openSUSE Member > > GPG KEY : D5C9B751C4653227 > > irc: tigerfoot > > -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot

2 2

[opensuse-kernel] No PAE support in 13.1 live images?
by James Mason 30 Oct '13

30 Oct '13

I noticed that the package lists for Live KDE and Live GNOME 32-bit images include kernel-default, instead of kernel-desktop[1], as the 64-bit images do. I checked the kernel configs[2] to see what the specific differences were, and noted that the 32-bit kernel-default *does not* include PAE, but the 32-bit kernel-desktop does. So, in effect, the 32-bit Live images *do not* have PAE support! Is there a valid reason why we're using kernel-default instead of kernel-desktop in the 32-bit Live images, or is this a packaging bug? [1] https://build.opensuse.org/package/view_file/openSUSE:13.1:Live/package-lis… https://build.opensuse.org/package/view_file/openSUSE:13.1:Live/package-lis… [2] http://kernel.opensuse.org/cgit/kernel-source/tree/config/i386?h=openSUSE-1… -- James Mason Online Operations openSUSE Member SUSE jmason(a)suse.com (P)+1 360.752.6707 SUSE -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] ext4 file embedding in inode
by Andrey Borzenkov 29 Oct '13

29 Oct '13

В Sun, 27 Oct 2013 06:57:52 -0700 (PDT) Jos Poortvliet <jospoortvliet(a)gmail.com> пишет: > Hi all, > > A reminder: if you have not added things to > https://en.opensuse.org/openSUSE:Major_features please do so! > > And go over it to review what's there if you can. > I noticed "Ext4 introduces the embedding of very small files in the inode." Last time I looked e2fsprogs in Factory did not include version capable of enabling it. Did it change? Is it now enabled by default? This may be a problem as grub2 does not support it (I have a patch hanging around though ...) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] [RFC V4 PATCH 00/15] Signature verification of hibernate snapshot
by Lee, Chun-Yi 17 Oct '13

17 Oct '13

Hi experts, This patchset is the implementation for signature verification of hibernate snapshot image. The origin idea is from Jiri Kosina: Let EFI bootloader generate key-pair in UEFI secure boot environment, then pass it to kernel for sign/verify S4 image. Due to there have potential threat from the S4 image hacked, it may causes kernel lost the trust in UEFI secure boot. Hacker attack the S4 snapshot image in swap partition through whatever exploit from another trusted OS, and the exploit may don't need physical access machine. So, this patchset give the ability to kernel for parsing RSA private key from EFI bootloader, then using the private key to generate the signature of S4 snapshot image. Kernel put the signature to snapshot header, and verify the signature when kernel try to recover snapshot image to memory. How To Enable ============== Set CONFIG_SNAPSHOT_VERIFICATION kernel config to enable. And you can also choice which hash algorithm should snapshot be signed with. Then rebuild kernel. This function depends on EFI_STUB. Please note this function need UEFI bootloader's support to generate key-pair in UEFI secure boot environment, e.g. shim. Current shim implementation by Gary Lin: Git: https://github.com/lcp/shim/tree/s4-key-upstream RPM: https://build.opensuse.org/package/show/home:gary_lin:UEFI/shim Please use the shim from above URL if you want to try. Please remember add the hash of shim to db in UEFI BIOS because it didn't sign by Microsoft or any OSV key. The default behavior is taint kernel when signature check fail. If you want direct fail whole hibernate snapshot restore procedure when signature check does not pass, please use snapshot_sig_enforce kernel parameter or CONFIG_EFI_SECURE_BOOT_SNAPSHOT_SIG_ENFORCE config. If you want binding UEF secure boot with sig_enforce flag, then you can use CONFIG_EFI_SECURE_BOOT_SNAPSHOT_SIG_ENFORCE config. The sig_enforce flag will auto enabled when UEFI secure boot enabled. Behavior ========= The RSA key-pair are generated by EFI bootloader(e.g. shim) in UEFI secure boot environment, then put private key to S4SignKey, public key to S4WakeKey EFI variable. Kernel's behavior as following: + First, EFI stub kernel will check the following 2 EFI variable: S4SignKey-fe141863-c070-478e-b8a3-878a5dc9ef21 [BootService] S4WakeKey-fe141863-c070-478e-b8a3-878a5dc9ef21 [Runtime][Volatile] S4SignKey and S4WakeKey is a RSA key-pair: - S4SignKey is a private key that's used to generate signature of S4 snapshot. The blob format of S4SignKey is PKCS#8 _uncompressed_ format, it should packaged a RSA private key that's followed PKCS#1. - S4WakeKey is a public key that's used to verify signature of S4 snapshot. The blob format of S4WakeKey is X.509 format, it should packaged a RSA public key that's followed PKCS#1. + EFI stub kernel will load the S4SignKey blob to RAM before ExitBootServices, then copy to a memory page that's maintained by hibernate_key.c. This private key will be used to sign snapshot when hibernate launched. + When sig_enforce flag set to TRUE, means force check verification pass: - If kernel didn't find S4 key-pair, then kernel will block hibernate functions including kernel space and userspace hibernate. - If snapshot signature check fail when hibernate resume, the snapshot restore procedure will fail and running normal boot process. + When sig_enforce flag set to FALSE, means not force the verification pass: - If kernel didn't find S4 key-pair, then the hibernate function still available. But kernel will be tainted after hibernate resume. - If snapshot signature check fail when hibernate resume, the snapshot restore procedure will allow continue. But kernel will be tainted. On EFI bootloader side, the behavior as following: + EFI bootloader must generate RSA key-pair when: - First time boot, bootloader generate key-pair when didn't find it. - Bootloader need re-generate after found GenS4Key efi variable from OS: GenS4Key-fe141863-c070-478e-b8a3-878a5dc9ef21 [Runtime][Non-Volatile] The size of GenS4Key is 1 byte, OS(kernel or userland tool) will set it to "1" for notify efi bootloader regenerate key-pair. - If re-generate key-pair, bootloader need store the new public key to EFI bootservices variable by itself, e.g. store to NextWakeKey variable When system resumed from hibernate, bootloader need copy public key from NextWakeKey to S4WakeKey, then kernel will use it to verify snapshot image. Implementation ============== Whole implementation including 3 parts: shim, asymmetric keys and hibernate: + shim: Current solution implemented by Gary Lin: https://github.com/lcp/shim/tree/s4-key-upstream Please use shim from the above URL if you want to try. Please remember add this shim to db because it didn't sign by Microsoft or any OSV key. + Asymmetric keys: This patchset implemented uncompressed PKCS#8 and RSA private key parser, it also implement the signature generation operation of RSASSA-PKCS1-v_5 in PKCS#1 spec. [RFC3447 sec 8.2.2] Set CONFIG_PKCS8_PRIVATE_KEY_INFO_PARSER=y will give kernel the abilities to parsing private key in uncompressed PKCS#8 blob and generate signature. + Hibernate: Set CONFIG_SNAPSHOT_VERIFICATION=y will enable the function of snapshot signature generation and verification. I reserved 512 byes size in snapshot header for store the signature that's generated from the digest with SHA algorithms. For adapt S4 signature check to secure boot, It Base on Matthew Garrett's 2 patches in "[PATCH] Add additional security checks when module loading is restricted" series: https://lkml.org/lkml/2013/8/19/331 [PATCH 01/10] Add secure_modules() call [PATCH V3 11/11] Add option to automatically enforce module signatures when in Secure Boot mode Please help review this RFC patchset! Appreciate for any comments! V4: - Cleaned source code, use helper functions to reduce #ifdef chunk. - Introduced sig_enforce flag, taint kernel when signature check fail. - Use forward_info structure to maintain the empty of forward information and new sign key from boot kernel to resume target kernel. - Use efivar API to access S4WakeKey variable. - Call set_key_regen_flag() to set key-pair regeneration flag in hibernate.c and user.c V3: - Load S4 sign key before ExitBootServices in efi stub. - In Makefile, moved hibernate_keys.o before hibernate.o for load S4 sign key before check hibernate image. It makes sure the new sign key will be transfer to resume target kernel. - Set "depends on EFI_STUB" in Kconfig. V2: - Moved SNAPSHOT_VERIFICATION kernel config to earlier patch. - Add dummy functions to simplify the ifdef check. - Sent to opensuse-kernel(a)opensuse.org for review: http://lists.opensuse.org/opensuse-kernel/2013-08/msg00025.html V1: - Internal review - github: https://github.com/joeyli/linux-s4sign/commits/devel-s4sign Lee, Chun-Yi (15): asymmetric keys: add interface and skeleton for implement signature generation asymmetric keys: implement EMSA_PKCS1-v1_5-ENCODE in rsa asymmetric keys: separate the length checking of octet string from RSA_I2OSP asymmetric keys: implement OS2IP in rsa asymmetric keys: implement RSASP1 asymmetric keys: support parsing PKCS #8 private key information asymmetric keys: explicitly add the leading zero byte to encoded message Hibernate: introduced RSA key-pair to verify signature of snapshot Hibernate: generate and verify signature of snapshot Hibernate: Avoid S4 sign key data included in snapshot image Hibernate: taint kernel when signature check fail Hibernate: show the verification time for monitor performance Hibernate: introduced SNAPSHOT_SIG_HASH config for select hash algorithm Hibernate: notify bootloader regenerate key-pair for snapshot verification Hibernate: adapt to UEFI secure boot with signature check Documentation/kernel-parameters.txt | 7 + arch/x86/Kconfig | 11 + arch/x86/boot/compressed/eboot.c | 92 +++++++ arch/x86/include/asm/efi.h | 9 + arch/x86/include/uapi/asm/bootparam.h | 1 + arch/x86/kernel/setup.c | 7 + arch/x86/platform/efi/efi.c | 68 +++++ crypto/asymmetric_keys/Kconfig | 11 + crypto/asymmetric_keys/Makefile | 16 + crypto/asymmetric_keys/pkcs8.asn1 | 19 ++ crypto/asymmetric_keys/pkcs8_info_parser.c | 152 ++++++++++ crypto/asymmetric_keys/pkcs8_parser.h | 23 ++ crypto/asymmetric_keys/pkcs8_private_key.c | 148 ++++++++++ crypto/asymmetric_keys/pkcs8_rsakey.asn1 | 29 ++ crypto/asymmetric_keys/private_key.h | 29 ++ crypto/asymmetric_keys/public_key.c | 32 +++ crypto/asymmetric_keys/rsa.c | 296 +++++++++++++++++++- crypto/asymmetric_keys/signature.c | 28 ++ include/crypto/public_key.h | 28 ++ include/keys/asymmetric-subtype.h | 6 + include/linux/efi.h | 25 ++ include/linux/kernel.h | 1 + include/linux/suspend.h | 7 + kernel/panic.c | 2 + kernel/power/Kconfig | 77 +++++- kernel/power/Makefile | 1 + kernel/power/hibernate.c | 23 ++- kernel/power/hibernate_keys.c | 410 ++++++++++++++++++++++++++++ kernel/power/main.c | 7 +- kernel/power/power.h | 62 +++++ kernel/power/snapshot.c | 323 ++++++++++++++++++++++- kernel/power/swap.c | 4 + kernel/power/user.c | 14 +- 33 files changed, 1946 insertions(+), 22 deletions(-) create mode 100644 crypto/asymmetric_keys/pkcs8.asn1 create mode 100644 crypto/asymmetric_keys/pkcs8_info_parser.c create mode 100644 crypto/asymmetric_keys/pkcs8_parser.h create mode 100644 crypto/asymmetric_keys/pkcs8_private_key.c create mode 100644 crypto/asymmetric_keys/pkcs8_rsakey.asn1 create mode 100644 crypto/asymmetric_keys/private_key.h create mode 100644 kernel/power/hibernate_keys.c -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

12 44

[opensuse-kernel] 13.1 RC1: unable to rename any directory or file on btrfs
by Andrey Borzenkov 17 Oct '13

17 Oct '13

Is it expected? I obviously do have enough space and can create (and delete) files and directories but am not able to rename anything. Do I need to open bug report? linux-1a7f:~ # btrfs filesystem df /mnt System: total=4.00MiB, used=4.00KiB Data+Metadata: total=5.00MiB, used=60.00KiB linux-1a7f:~ # cd /mnt/dir1/ linux-1a7f:/mnt/dir1 # ls -l total 0 drwxr-xr-x 1 root root 0 Oct 14 09:43 dir2 -rw-r--r-- 1 root root 0 Oct 14 09:43 file1 linux-1a7f:/mnt/dir1 # mv dir2 dir3 mv: cannot move ‘dir2’ to ‘dir3’: No space left on device linux-1a7f:/mnt/dir1 # mv file1 file2 mv: cannot move ‘file1’ to ‘file2’: No space left on device linux-1a7f:/mnt/dir1 # echo ghdfgshf hdsghfj > file2 linux-1a7f:/mnt/dir1 # mkdir dir3 linux-1a7f:/mnt/dir1 # ls -l total 4 drwxr-xr-x 1 root root 0 Oct 14 09:43 dir2 drwxr-xr-x 1 root root 0 Oct 14 10:58 dir3 -rw-r--r-- 1 root root 0 Oct 14 09:43 file1 -rw-r--r-- 1 root root 17 Oct 14 10:58 file2 linux-1a7f:/mnt/dir1 # btrfs filesystem df /mnt System: total=4.00MiB, used=4.00KiB Data+Metadata: total=5.00MiB, used=60.00KiB linux-1a7f:~ # uname -a Linux linux-1a7f 3.11.3-1-pae #1 SMP Wed Oct 2 05:54:02 UTC 2013 (485f0d1) i686 i686 i386 GNU/Linux -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 11