From: JW <jw@centraltexasit.com>
To: selinux@tycho.nsa.gov
Subject: How to go about mixing kernel patches...
Date: Fri, 31 May 2002 21:39:56 -0500 [thread overview]
Message-ID: <200205312140.02418.jw@centraltexasit.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I hope no one minds to mposting this here, if you do, flame away.
My first difficulty it appling the SE Linux patch to the SuSE-patched kernel.
I applied lsm-2.4-2002050211.patch.gz to vanila 2.4.18 and they apply perfectly.
I applied it to linux-2.4.18-SuSE and got some errors, producing the following rejects:
linux-2.4.18.SuSE/fs/dquot.c.rej
linux-2.4.18.SuSE/fs/namei.c.rej
linux-2.4.18.SuSE/fs/inode.c.rej
linux-2.4.18.SuSE/mm/memory.c.rej
linux-2.4.18.SuSE/mm/mprotect.c.rej
linux-2.4.18.SuSE/mm/filemap.c.rej
linux-2.4.18.SuSE/net/socket.c.rej
linux-2.4.18.SuSE/arch/i386/kernel/entry.S.rej
linux-2.4.18.SuSE/arch/ia64/kernel/entry.S.rej
linux-2.4.18.SuSE/init/main.c.rej
linux-2.4.18.SuSE/kernel/fork.c.rej
linux-2.4.18.SuSE/kernel/sched.c.rej
linux-2.4.18.SuSE/Makefile.rej
linux-2.4.18.SuSE/include/linux/fs.h.rej
Or if this helps any:
jw:/work/dl/se_linux/se_build/linux-2.4.18.SuSE # zcat ../../opt5/all-opt-4-together/patches/lsm-2.4-2002050211.patch.gz | patch -s -p1
1 out of 3 hunks FAILED -- saving rejects to file Makefile.rej
1 out of 1 hunk FAILED -- saving rejects to file arch/i386/kernel/entry.S.rej
1 out of 1 hunk FAILED -- saving rejects to file arch/ia64/kernel/entry.S.rej
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
1 out of 1 hunk ignored -- saving rejects to file fs/binfmt_elf.c.rej
1 out of 2 hunks FAILED -- saving rejects to file fs/dquot.c.rej
1 out of 3 hunks FAILED -- saving rejects to file fs/inode.c.rej
1 out of 22 hunks FAILED -- saving rejects to file fs/namei.c.rej
1 out of 6 hunks FAILED -- saving rejects to file include/linux/fs.h.rej
1 out of 2 hunks FAILED -- saving rejects to file init/main.c.rej
1 out of 4 hunks FAILED -- saving rejects to file kernel/fork.c.rej
1 out of 7 hunks FAILED -- saving rejects to file kernel/sched.c.rej
1 out of 3 hunks FAILED -- saving rejects to file mm/filemap.c.rej
1 out of 1 hunk FAILED -- saving rejects to file mm/memory.c.rej
1 out of 2 hunks FAILED -- saving rejects to file mm/mprotect.c.rej
1 out of 15 hunks FAILED -- saving rejects to file net/socket.c.rej
At this point I'm presuming the the correct course of action is to diff those files one at a time between the "good" patched {.c|.h} files and the "bad" suse-patched {.c|.h} files.
Would there be any benefit to try to do the opposite, i.e. apply the LSM patches first, and the SuSE patches second?
I'm a little worried since I have to mix 3 patches actually. I suppose there's not much chance of the actual se-linux patches applying to my mixed lsm/suse kernel?
Sorry to ask such basic questions, I've never had to do something like this before -- but I'm detirmined to do it right.
If any one has advise as far as how to go about this, I'd really appreciate hearing from you.
Thanks!
- --
- ----------------------------------------------------
Jonathan Wilson
System Administrator
Cedar Creek Software http://www.cedarcreeksoftware.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8+DQCQ5u80xXOLBcRAoBCAKC7v3Ta7boFkXltryIjtOj1wohx5ACfesN3
LLlU60flwIRnTs4Ylkon2RU=
=ALT7
-----END PGP SIGNATURE-----
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2002-06-01 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 2:39 JW [this message]
2002-06-01 7:21 ` How to go about mixing kernel patches Russell Coker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200205312140.02418.jw@centraltexasit.com \
--to=jw@centraltexasit.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.