Re: kernel >= 2.6.20 in SL5
2009/12/17 Jim Green : > Thank you to all who replied. I am, you probably guessed, a bit of > a RH virgin and didn't know about the heavy patching applied to > kernels -- I'm from the Debian world where a range of kernels is always > available and trying them out is just an apt-get away. Please excuse > my faux pas. No problem. :-) > Garrett Holmstrom: >> The right way to fix this problem would be to file a bug against the >> kernel package so upstream can backport a fix. They add bugfixes >> and new features by patching the same kernel version so the release >> can keep the same version throughout its lifetime while still remaining >> useful. > > I'll do that, but do you mean the kernel devs at kernel.org > or RH or SL? Essentially TUV to SL, in words rather than acronyms, Red Hat -- via https://bugzilla.redhat.com/frontpage.cgi It might be worth being aware of the RHEL 5 testing kernels that are made available by Don Zickus -- http://people.redhat.com/dzickus/el5/ Usually the patches that are present in Don's testing kernels eventually make their way into the next RHEL kernel release and hence the SL (and CentOS) kernels. > Cheers, and thanks again for all the help You're welcome. Alan.
Re: kernel >= 2.6.20 in SL5
Thank you to all who replied. I am, you probably guessed, a bit of a RH virgin and didn't know about the heavy patching applied to kernels -- I'm from the Debian world where a range of kernels is always available and trying them out is just an apt-get away. Please excuse my faux pas. Following your advice I've searched around the RH site and found the most recent kernels I could, I've tested 2.6.18-181.el5 2.6.18-175.el5.jtltest.96 2.6.18-164.6.1.el5 2.6.18-128.7.1.el5 2.6.18-53.1.4.el5 behavior is identical for all of them: /home is nfs4 automounted, authentication is kerberos over LDAP. > ls -l /home drwx-- 2 user1 user172 Dec 16 16:51 user1 drwxrwx--- 2 user2 userall 72 Dec 16 16:51 user2 > ls -l /home/user2 rw-rwuser2 userall 0 Dec 17 11:33 group-writable login as user1 > groups user1 userall > pwd /home/user1 > echo "time to die" > ../user2/group-writable -> kernel panic gss_wrap_req [auth_rpcgss] cache_alloc_refill gss_wrap_req [auth_rpcgss] nfs4_xdr_enc_write [nfs] rpcauth_wrap_req [sunrpc] nfs4_xdr_enc_write [nfs] call_transmit [sunrpc] __rpc_execute [sunrpc] nfs_execute_write [nfs] nfs_flush_one [nfs] nfs_flush_list [nfs] nfs_flush_one [nfs] nfs_sync_inode_wait [nfs] nfs_do_fsync [nfs] nfs_file_flush [nfs] filp_close sys_dup2 syscal_call EIP kunmap_atomic kernel panic -- not syncing: Fatal exception Bizzarely, puting the killer command into a script (just to save time) means no kernel panic, I ran the script many times. Garrett Holmstrom: > The right way to fix this problem would be to file a bug against the > kernel package so upstream can backport a fix. They add bugfixes > and new features by patching the same kernel version so the release > can keep the same version throughout its lifetime while still remaining > useful. I'll do that, but do you mean the kernel devs at kernel.org or RH or SL? Cheers, and thanks again for all the help Jim
Re: kernel >= 2.6.20 in SL5
Alan Bartlett schrieb: > 2009/12/16 Jim Green : > >> I'm trying to set up an SL5 client for a kerberos/LDAP/NFS4 server. I'm >> getting >> a kernel panic on the client in certain situations (writing to a file >> which I do not >> own but do have group write permissions) and from the oops I think that this >> is a kernel bug fixed in 2.6.20. Sadly, yum shows me only 2.6.18 kernels and >> the problem persists on the most recent (2.6.18-164.6.1.el15) >> >> So to my question : How can one install a kernel >= 2.6.20 on SL5 ? >> I couldn't find SL rpms/srpms and googling for the experience of others >> wanting to do this turns up little useful info. > > Jim, > > Please read TUV's policy on backporting [1]. > > You should also realise it is not the mainline kernel-2.6.18 but is > kernel-2.6.18-164.6.1.el5 with somewhere in the order of 2000 patches > applied to the original mainline kernel. The "EXTRAVERSION" of > "-164.6.1.el5" makes all the difference. Yep, and there will be an 164.9.1 kernel in a few days which fix a oops in nfs4 client code, the release note from TUV just went out. Sincerly, Klaus <> signature.asc Description: OpenPGP digital signature
Re: kernel >= 2.6.20 in SL5
2009/12/16 Jim Green : > I'm trying to set up an SL5 client for a kerberos/LDAP/NFS4 server. I'm > getting > a kernel panic on the client in certain situations (writing to a file > which I do not > own but do have group write permissions) and from the oops I think that this > is a kernel bug fixed in 2.6.20. Sadly, yum shows me only 2.6.18 kernels and > the problem persists on the most recent (2.6.18-164.6.1.el15) > > So to my question : How can one install a kernel >= 2.6.20 on SL5 ? > I couldn't find SL rpms/srpms and googling for the experience of others > wanting to do this turns up little useful info. Jim, Please read TUV's policy on backporting [1]. You should also realise it is not the mainline kernel-2.6.18 but is kernel-2.6.18-164.6.1.el5 with somewhere in the order of 2000 patches applied to the original mainline kernel. The "EXTRAVERSION" of "-164.6.1.el5" makes all the difference. Regards, Alan. [1] http://www.redhat.com/security/updates/backporting/
Re: kernel >= 2.6.20 in SL5
From: "Jim Green" Date: Wednesday, December 16, 2009 9:59 AM > I'm trying to set up an SL5 client for a kerberos/LDAP/NFS4 server. I' m > getting > a kernel panic on the client in certain situations (writing to a file > which I do not > own but do have group write permissions) and from the oops I think that > this > is a kernel bug fixed in 2.6.20. Sadly, yum shows me only 2.6.18 kerne ls > and > the problem persists on the most recent (2.6.18-164.6.1.el15) > > So to my question : How can one install a kernel >= 2.6.20 on SL5 ? > I couldn't find SL rpms/srpms and googling for the experience of others > wanting to do this turns up little useful info. The right way to fix this problem would be to file a bug against the kern el package so upstream can backport a fix. They add bugfixes and new featur es by patching the same kernel version so the release can keep the same vers ion throughout its lifetime while still remaining useful. I once got curious and tried compiling and running a newer Fedora kernel on my RHEL system, and while I got it to work, running a newer kernel versio n is generally a very bad idea because the rest of the system is built with the assumption that it's running under Linux 2.6.18. You would likely be shooting yourself in the foot. -- Garrett Holmstrom University of Minnesota School of Physics and Astronomy Systems Staff
kernel >= 2.6.20 in SL5
Hi all I'm trying to set up an SL5 client for a kerberos/LDAP/NFS4 server. I'm getting a kernel panic on the client in certain situations (writing to a file which I do not own but do have group write permissions) and from the oops I think that this is a kernel bug fixed in 2.6.20. Sadly, yum shows me only 2.6.18 kernels and the problem persists on the most recent (2.6.18-164.6.1.el15) So to my question : How can one install a kernel >= 2.6.20 on SL5 ? I couldn't find SL rpms/srpms and googling for the experience of others wanting to do this turns up little useful info. Any pointers on this would earn my eternal gratitude ! Thanks in advance Jim
