Vanilla kernel patch

Vanilla kernel patch

[Francesco Biscani]

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Hi,

yesterday I threw together a patchset to enable reiser4 for the vanilla 
2.6.9-rc3 kernel. Basically I just downloaded the broken-out -mm2 patch and 
applied the reiser4 patches in the order described by the "patch-series" 
file. I did this because -mm has been too unstable for me and I don't need al 
the features that can be found in -cko or -klak or others patchsets.

I would like to know how many troubles I'm running into :) So far the kernel 
seems to go fine and dandy, and some fsck's did not reveal any problem. I had 
to manually edit the reiser4-reget-something patch, which failed because it 
wanted to use the write_lock function instead of the spin_lock function that 
is found in vanilla -rc3. Also, I had to apply two non-reiser4 patches. The 
first added the "i_sb_list" member to the inode structure (it was the 
inodes-speedup patch), the second enabled generic acl and got rid of the 
"undeclared function" warning gcc gave. Now all reiser4 stuff compiles with 
no warnings at all.

What are the pitfalls I'm falling in, doing this? Is this safe or is there 
stuff in -mm that is absolutely needed by reiser4?

Thanks!

-- 
Dr. Francesco Biscani

Dipartimento di Astronomia
Università di Padova

biscani@pd.astro.it

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

Re: Vanilla kernel patch

[Milan Holzäpfel]

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

On Thu, 7 Oct 2004 14:02:27 +0200
Francesco Biscani <biscani@pd.astro.it> wrote:

> Hi,
> 
> yesterday I threw together a patchset to enable reiser4 for the vanilla 
> 2.6.9-rc3 kernel.  [...]

I did the same some time ago with the last official snapshot, which has
worked fine for me so far.  reiser4 is used for my gentoo portage tree,
my /var filesystem, for a partition where portage compiles the packages
on and for Squid's cache (Squid is a http and ftp proxy).

> What are the pitfalls I'm falling in, doing this? Is this safe or is there 
> stuff in -mm that is absolutely needed by reiser4?

Well I'd make the guess that if there is something in the mm kernel
which is absolutely needed by reiser4 then the thing won't link or you
will be unable to load the module if you chose to compile it as a
module.

> Thanks!

Regards,
Milan


- -- 

                   Milan Holzäpfel alias jagdfalke alias jag

Antworten direkt an mich                             Answers directly to me
gehen bitte an eine Addresse,                        go to an address one
die man hier finden kann:                            can find here, please:

Kontaktinfos sowie                                   Contact infos as well as
Öff GnuPG-Schlüssel    <URL:http://con.mjh.name/>    GnuPG Public Key
GnuPG Fingerabdruck     4C8A 5FAF 5D32 6125 89D1     GnuPG Fingerprint
                        0CE5 DB0C AF4F 6583 7966


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBZqRF2wyvT2WDeWYRAvvvAKDjc0RjCJoA9UdcJvSk7+gtWJFJ/ACeO29S
FPoE3gdyY49VyNt/y57KLj4=
=Ms9R
-----END PGP SIGNATURE-----

Re: Vanilla kernel patch

[Francesco Biscani]

[-- Attachment #1: Type: text/plain, Size: 880 bytes --]

Thanks for your response Milan.

On Friday 08 October 2004 16:29, Milan Holzäpfel wrote:
> > What are the pitfalls I'm falling in, doing this? Is this safe or is
> > there stuff in -mm that is absolutely needed by reiser4?
>
> Well I'd make the guess that if there is something in the mm kernel
> which is absolutely needed by reiser4 then the thing won't link or you
> will be unable to load the module if you chose to compile it as a
> module.

That's my guess too. I've also noticed that apart from the changes I talked 
about in my previous mail, the reiser4 patches applied cleanly.

However I still would like to hear from the devs about this issue. I've got 
my / partition on reiser4, so forgive me if I'm pretty picky about this ;-)

Best regards,

-- 
Dr. Francesco Biscani

Dipartimento di Astronomia
Università di Padova

biscani@pd.astro.it

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]