Reiser4 module and 2.6.29-x-default kernel

Reiser4 module and 2.6.29-x-default kernel

[doiggl]

Hello,
How can I manually create a installable reiser4 rpm module for a new
kernel, because the opensuse build service seems stuck on a older kernel .
I need all of the steps please, (commands please) so I can create the
installable rpm module.

2. In the past, I've used the reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3
(2.6.27.7-9-default) opensuse 11.1 with good success and has worked well
for me.

# uname -a
Linux test 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64
x86_64 GNU/Linux

# rpm -ivhU reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3 DSA
signature: NOKEY, key ID 74de2879
Preparing...                ###########################################
[100%]
   1:reiser4-kmp-default    ###########################################
[100%]
24831 blocks
24831 blocks

#  modprobe -v  reiser4
insmod
/lib/modules/2.6.27.7-9-default/kernel/lib/zlib_deflate/zlib_deflate.ko
insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_compress.ko
insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_decompress.ko
insmod /lib/modules/2.6.27.7-9-default/updates/reiser4.ko

# rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
DSA signature: NOKEY, key ID 74de2879
/lib/modules/2.6.27.7-9-default
/lib/modules/2.6.27.7-9-default/updates
/lib/modules/2.6.27.7-9-default/updates/reiser4.ko

3. My new system details with 11.2-Milestone1 (new)
===================================================
I want to install reiser 4 on it reiser4-kmp-default with 2.6.29-XX-default

3a. System installed with 11.2-Milestone1 -
http://download.opensuse.org/distribution/11.2-Milestone1/iso/openSUSE-KDE4-LiveCD-Build0067-i686.iso
# uname -a
Linux linux 2.6.29-6-default #1 SMP 2009-03-24 15:38:18 +0100 x86_64
x86_64 x86_64 GNU/Linux

How can I manually create a installable reiser4 rpm module.
I need all of the steps please, (commands please) so I can create the rpm
module with the three files (see below).

Other references I looked at but I did not understand the reiser4.spec and
how the files (see below) are generated and packaged for a newer kernel..

# rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
DSA signature: NOKEY, key ID 74de2879
/lib/modules/2.6.27.7-9-default
/lib/modules/2.6.27.7-9-default/updates
/lib/modules/2.6.27.7-9-default/updates/reiser4.ko

https://build.opensuse.org/package/view_file?file=reiser4.spec&package=reiser4-kmp&project=drivers%3Afilesystems

Thankyou for your help and time.
Glenn

Re: Reiser4 module and 2.6.29-x-default kernel

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

doiggl@velocitynet.com.au wrote:
> Hello,
> How can I manually create a installable reiser4 rpm module for a new
> kernel, because the opensuse build service seems stuck on a older kernel .
> I need all of the steps please, (commands please) so I can create the
> installable rpm module.

Hi Glenn -

I'm afraid it's not as simple as a series of commands. I do need to
update the patch to the 2.6.29 version which doesn't have the
- ->commit_write and ->prepare_write hooks that have been removed. The
other thing is that it needs more support in the kernel itself.
Previously it was limited to exports and adding a new hook, which I
could accept without much worry. I'm concerned about whether
set_buffers_dirty_notag() will make it upstream and I'm uncertain of the
interactions.

Edward - What's the reasoning behind it? Has it been submitted upstream
yet? Is it possible to use reiser4_set_dirty_pages creatively to get
the same effect?

- -Jeff

> 2. In the past, I've used the reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3
> (2.6.27.7-9-default) opensuse 11.1 with good success and has worked well
> for me.
> 
> # uname -a
> Linux test 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64
> x86_64 GNU/Linux
> 
> # rpm -ivhU reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3 DSA
> signature: NOKEY, key ID 74de2879
> Preparing...                ###########################################
> [100%]
>    1:reiser4-kmp-default    ###########################################
> [100%]
> 24831 blocks
> 24831 blocks
> 
> #  modprobe -v  reiser4
> insmod
> /lib/modules/2.6.27.7-9-default/kernel/lib/zlib_deflate/zlib_deflate.ko
> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_compress.ko
> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_decompress.ko
> insmod /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
> 
> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
> DSA signature: NOKEY, key ID 74de2879
> /lib/modules/2.6.27.7-9-default
> /lib/modules/2.6.27.7-9-default/updates
> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
> 
> 3. My new system details with 11.2-Milestone1 (new)
> ===================================================
> I want to install reiser 4 on it reiser4-kmp-default with 2.6.29-XX-default
> 
> 3a. System installed with 11.2-Milestone1 -
> http://download.opensuse.org/distribution/11.2-Milestone1/iso/openSUSE-KDE4-LiveCD-Build0067-i686.iso
> # uname -a
> Linux linux 2.6.29-6-default #1 SMP 2009-03-24 15:38:18 +0100 x86_64
> x86_64 x86_64 GNU/Linux
> 
> How can I manually create a installable reiser4 rpm module.
> I need all of the steps please, (commands please) so I can create the rpm
> module with the three files (see below).
> 
> Other references I looked at but I did not understand the reiser4.spec and
> how the files (see below) are generated and packaged for a newer kernel..
> 
> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
> DSA signature: NOKEY, key ID 74de2879
> /lib/modules/2.6.27.7-9-default
> /lib/modules/2.6.27.7-9-default/updates
> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
> 
> https://build.opensuse.org/package/view_file?file=reiser4.spec&package=reiser4-kmp&project=drivers%3Afilesystems
> 
> Thankyou for your help and time.
> Glenn
> 


- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoWqqUACgkQLPWxlyuTD7IPGACZAWHkFYlr/FwNCUbW4XaDOhPW
qNkAn2XgJ2ycLXHzQ/pH1ETux6J3O2NH
=nchX
-----END PGP SIGNATURE-----

Re: Reiser4 module and 2.6.29-x-default kernel

[Ralph Ulrich]

ftp://ftp.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-
for-2.6/reiser4-for-2.6.29.patch.bz2

doiggl@velocitynet.com.au Freitag 22 Mai 2009 15:09:

> Hello,
> How can I manually create a installable reiser4 rpm module for a new
> kernel, because the opensuse build service seems stuck on a older
> kernel . I need all of the steps please, (commands please) so I can
> create the installable rpm module.
> 
> 2. In the past, I've used the
> reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3 (2.6.27.7-9-default)

With opensuse 11.2 you must patch the kernel source 2.6.29 and compile 
for your own. ...esay!

But I do not know much about the problems Jeff talked about...

Ralph

Re: Reiser4 module and 2.6.29-x-default kernel

[Edward Shishkin]

Jeff Mahoney wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> doiggl@velocitynet.com.au wrote:
>   
>> Hello,
>> How can I manually create a installable reiser4 rpm module for a new
>> kernel, because the opensuse build service seems stuck on a older kernel .
>> I need all of the steps please, (commands please) so I can create the
>> installable rpm module.
>>     
>
> Hi Glenn -
>
>   

Hello everyone.

> I'm afraid it's not as simple as a series of commands. I do need to
> update the patch to the 2.6.29 version

 ah, you maintain 2.6.small_nr + series of patches..?

>  which doesn't have the
> - ->commit_write and ->prepare_write hooks that have been removed.

this goes here:
http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-adjust-to-the-new-aops.patch

>  The
> other thing is that it needs more support in the kernel itself.
> Previously it was limited to exports and adding a new hook, which I
> could accept without much worry. I'm concerned about whether
> set_buffers_dirty_notag() will make it upstream and I'm uncertain of the
> interactions.
>   

I think it'll be pushed to upstream simultaneously with reiser4,
unless someone needs to not tag every dirty page in the radix tree..

> Edward - What's the reasoning behind it?

The reason is to reduce a cost of maintenance.

Since reiser4_set_page_internal() is not in vfs library
bad things are bound to happen. For example, set_page_dirty()
and friends were modified by vfs folks to update dirty pages
accounting and of course nobody knew that there are other
"friends" in reiser4 code, so I have spent a lot of time to figure
out why oom kills processes of dbench 190...

>  Has it been submitted upstream
> yet?

Nup, this is in -mm

> Is it possible to use reiser4_set_dirty_pages creatively to get
> the same effect?
>   

Sure.
Just modify it to update dirty page accounting
(2 strings or so need to be added).
Note, that there were 2 friends in reiser4 to modify:
reiser4_set_page_dirty() and reiser4_set_page_dirty_internal().

Edward.

> - -Jeff
>
>   
>> 2. In the past, I've used the reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3
>> (2.6.27.7-9-default) opensuse 11.1 with good success and has worked well
>> for me.
>>
>> # uname -a
>> Linux test 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64
>> x86_64 GNU/Linux
>>
>> # rpm -ivhU reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
>> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3 DSA
>> signature: NOKEY, key ID 74de2879
>> Preparing...                ###########################################
>> [100%]
>>    1:reiser4-kmp-default    ###########################################
>> [100%]
>> 24831 blocks
>> 24831 blocks
>>
>> #  modprobe -v  reiser4
>> insmod
>> /lib/modules/2.6.27.7-9-default/kernel/lib/zlib_deflate/zlib_deflate.ko
>> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_compress.ko
>> insmod /lib/modules/2.6.27.7-9-default/kernel/lib/lzo/lzo_decompress.ko
>> insmod /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>>
>> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
>> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
>> DSA signature: NOKEY, key ID 74de2879
>> /lib/modules/2.6.27.7-9-default
>> /lib/modules/2.6.27.7-9-default/updates
>> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>>
>> 3. My new system details with 11.2-Milestone1 (new)
>> ===================================================
>> I want to install reiser 4 on it reiser4-kmp-default with 2.6.29-XX-default
>>
>> 3a. System installed with 11.2-Milestone1 -
>> http://download.opensuse.org/distribution/11.2-Milestone1/iso/openSUSE-KDE4-LiveCD-Build0067-i686.iso
>> # uname -a
>> Linux linux 2.6.29-6-default #1 SMP 2009-03-24 15:38:18 +0100 x86_64
>> x86_64 x86_64 GNU/Linux
>>
>> How can I manually create a installable reiser4 rpm module.
>> I need all of the steps please, (commands please) so I can create the rpm
>> module with the three files (see below).
>>
>> Other references I looked at but I did not understand the reiser4.spec and
>> how the files (see below) are generated and packaged for a newer kernel..
>>
>> # rpm -qlp reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm
>> warning: reiser4-kmp-default-0.1_2.6.27.7_9.1-27.3.x86_64.rpm: Header V3
>> DSA signature: NOKEY, key ID 74de2879
>> /lib/modules/2.6.27.7-9-default
>> /lib/modules/2.6.27.7-9-default/updates
>> /lib/modules/2.6.27.7-9-default/updates/reiser4.ko
>>
>> https://build.opensuse.org/package/view_file?file=reiser4.spec&package=reiser4-kmp&project=drivers%3Afilesystems
>>
>> Thankyou for your help and time.
>> Glenn
>>
>>     
>
>
> - --
> Jeff Mahoney
> SUSE Labs
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkoWqqUACgkQLPWxlyuTD7IPGACZAWHkFYlr/FwNCUbW4XaDOhPW
> qNkAn2XgJ2ycLXHzQ/pH1ETux6J3O2NH
> =nchX
> -----END PGP SIGNATURE-----
>
>   

Re: Reiser4 module and 2.6.29-x-default kernel

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward Shishkin wrote:
> Jeff Mahoney wrote:
> doiggl@velocitynet.com.au wrote:
>  
>>>> Hello,
>>>> How can I manually create a installable reiser4 rpm module for a new
>>>> kernel, because the opensuse build service seems stuck on a older
>>>> kernel .
>>>> I need all of the steps please, (commands please) so I can create the
>>>> installable rpm module.
>>>>     
> 
> Hi Glenn -
> 
>   
> 
>> Hello everyone.
> 
> I'm afraid it's not as simple as a series of commands. I do need to
> update the patch to the 2.6.29 version
> 
>> ah, you maintain 2.6.small_nr + series of patches..?

I'm one of the maintainers of the SUSE kernels. For current Factory,
that means 2.6.30-rc6-git3 plus about 270 patches.

In this case, though, I just meant that I take the patch from your FTP
repo and turn it into a tarball for use in building an RPM. I take the
bits that aren't under fs/reiser4/ and apply them to our kernel tree so
users trying to use reiser4 aren't stuck having to rebuild their entire
kernel just to use it.

>  which doesn't have the
> ->commit_write and ->prepare_write hooks that have been removed.
> 
>> this goes here:
>> http://userweb.kernel.org/~akpm/mmotm/broken-out/reiser4-adjust-to-the-new-aops.patch

Yes, and as far as I saw, the current patch in the repo doesn't use them
either.


>  The
> other thing is that it needs more support in the kernel itself.
> Previously it was limited to exports and adding a new hook, which I
> could accept without much worry. I'm concerned about whether
> set_buffers_dirty_notag() will make it upstream and I'm uncertain of the
> interactions.
>   
> 
>> I think it'll be pushed to upstream simultaneously with reiser4,
>> unless someone needs to not tag every dirty page in the radix tree..
> 
> Edward - What's the reasoning behind it?
> 
>> The reason is to reduce a cost of maintenance.
> 
>> Since reiser4_set_page_internal() is not in vfs library
>> bad things are bound to happen. For example, set_page_dirty()
>> and friends were modified by vfs folks to update dirty pages
>> accounting and of course nobody knew that there are other
>> "friends" in reiser4 code, so I have spent a lot of time to figure
>> out why oom kills processes of dbench 190...
> 
>  Has it been submitted upstream
> yet?
> 
>> Nup, this is in -mm


Ok, if that's the goal, I can just track it when I update the reiser4 patch.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoWzxsACgkQLPWxlyuTD7KBqACgnERKLvlHHK7Tzhu/QSdQZBfE
CpkAnjge3xN0v0qGH35s/A67caQ4G90K
=Djsu
-----END PGP SIGNATURE-----

Re: Reiser4 module and 2.6.29-x-default kernel

[doiggl]

Hello,
Any progress on the Reiser4 module and 2.6.29-x-default kernel ?
Is this the one that will get updated at some point (see link)  ?
http://download.opensuse.org/repositories/drivers:/filesystems/openSUSE_Factory/x86_64/
Glenn

Edward Shishkin wrote:
> Jeff Mahoney wrote:
> Edward - What's the reasoning behind it?
>
>> The reason is to reduce a cost of maintenance.
>
>> Since reiser4_set_page_internal() is not in vfs library
>> bad things are bound to happen. For example, set_page_dirty()
>> and friends were modified by vfs folks to update dirty pages
>> accounting and of course nobody knew that there are other
>> "friends" in reiser4 code, so I have spent a lot of time to figure
>> out why oom kills processes of dbench 190...
>
>  Has it been submitted upstream
> yet?
>
>> Nup, this is in -mm

Ok, if that's the goal, I can just track it when I update the reiser4 patch.
- -Jeff

Re: Reiser4 module and 2.6.29-x-default kernel

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

doiggl@velocitynet.com.au wrote:
> Hello,
> Any progress on the Reiser4 module and 2.6.29-x-default kernel ?
> Is this the one that will get updated at some point (see link)  ?
> http://download.opensuse.org/repositories/drivers:/filesystems/openSUSE_Factory/x86_64/
> Glenn

Yep, that's the one. Sorry, I've been swamped lately so it may be a while.

- -Jeff


> Edward Shishkin wrote:
>> Jeff Mahoney wrote:
>> Edward - What's the reasoning behind it?
>>
>>> The reason is to reduce a cost of maintenance.
>>> Since reiser4_set_page_internal() is not in vfs library
>>> bad things are bound to happen. For example, set_page_dirty()
>>> and friends were modified by vfs folks to update dirty pages
>>> accounting and of course nobody knew that there are other
>>> "friends" in reiser4 code, so I have spent a lot of time to figure
>>> out why oom kills processes of dbench 190...
>>  Has it been submitted upstream
>> yet?
>>
>>> Nup, this is in -mm
> 
> Ok, if that's the goal, I can just track it when I update the reiser4 patch.
> - -Jeff
> 
> 


- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoeALMACgkQLPWxlyuTD7LFjwCfVNrfHikX22XkENz9Q2dL1btJ
GmkAn3XJFypMMdSdJN9Z4Vx3aY0H5zFZ
=H2EI
-----END PGP SIGNATURE-----

Re: Reiser4 module and 2.6.29-x-default kernel

[doiggl]

Hello,
I note from the build log that it fails.
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=reiser4-kmp&project=drivers%3Afilesystems&repository=openSUSE_Factory
note the errors on prepare_write & commit_write lines

 CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/carry_ops.o
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/carry_ops.c: In function
'find_left_neighbor':
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/carry_ops.c:81: warning:
suggest parentheses around operand of '!' or change '&' to '&&' or '!' to
'~'
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/carry_ops.c: In function
'find_right_neighbor':
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/carry_ops.c:205: warning:
suggest parentheses around operand of '!' or change '&' to '&&' or '!' to
'~'
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/lock.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/tree.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/context.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/tap.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/coord.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/block_alloc.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/txnmgr.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/kassign.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/flush.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/wander.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/eottl.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/search.o
CC [M] /usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/page_cache.o
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/page_cache.c:563: error:
unknown field 'prepare_write' specified in initializer
/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/page_cache.c:564: error:
unknown field 'commit_write' specified in initializer
make[3]: ***
[/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug/page_cache.o] Error 1
make[2]: *** [_module_/usr/src/packages/BUILD/reiser4-2.6.27/obj/debug]
Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
make: Leaving directory `/usr/src/linux-2.6.30-rc6-git3-4-obj/x86_64/debug'
error: Bad exit status from /var/tmp/rpm-tmp.67120 (%build)


RPM build errors:
cannot open Pubkeys index using db3 - No such file or directory (2)
Bad exit status from /var/tmp/rpm-tmp.67120 (%build)
System halted.


Jeff Mahoney wrote:
> Ok, if that's the goal, I can just track it when I update the reiser4
patch.
> - -Jeff
>