Bug 834789 - Zsmalloc kernel doesn't come with a licence information
Summary: Zsmalloc kernel doesn't come with a licence information
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-23 15:49 UTC by Antonio Augusto Santos
Modified: 2012-06-23 16:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-23 16:28:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Antonio Augusto Santos 2012-06-23 15:49:57 UTC
Description of problem:
Can't load module zcache nor zram on 3.4.x kernel series.
The problem appears to be with licence declaration of the module, as described here http://driverdev.linuxdriverproject.org/pipermail/devel/2012-June/027377.html and here http://lists.debian.org/debian-kernel/2012/06/msg00588.html .

Version-Release number of selected component (if applicable):
kernel-3.4.3-1.fc17.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install kmod-staging from rpmfusion, or build a new kernel with zsmalloc and zcache/zram as module
2. Try to load any of the modules
3.
  
Actual results:
# modprobe zcache
ERROR: could not insert 'zcache': No such file or directory
# tail /var/log/messages
zsmalloc: Unknown symbol alloc_vm_area (err 0)
zsmalloc: Unknown symbol free_vm_area (err 0)
zsmalloc: Unknown symbol __supported_pte_mask (err 0)


Expected results:
The module load without errors


Additional info:
There is already a patch for it: http://driverdev.linuxdriverproject.org/pipermail/devel/2012-June/027377.html. I haven't tried building it, and don't know if the patch has hit upstream.

Comment 1 Josh Boyer 2012-06-23 16:28:00 UTC
Fedora doesn't build or support ZSMALLOC and this is an issue that needs to be fixed upstream.


Note You need to log in before you can comment on or make changes to this bug.