gmane.linux.redhat.fedora.kernel http://blog.gmane.org/gmane.linux.redhat.fedora.kernel hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org 3.5 merge started http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3801 <pre>Mostly as FYI, I've started building the 3.5 merge window kernels today. The one building in Koji right now boots on my local x86_64 system without issue. I'm not sure if that trend will continue, but I plan on testing locally before I do koji builds. I've done the first round of Kconfig options settings. Secondary architectures, please review this and let me know if you want/need something set differently from how I have it. NOTE: The ARM configs are both confusing and too numerous, so I have not touched those. Also, the kernel-3.5.0-arm.config file seems to be dummy and winds up with a lot of options unset. The ARM team will need to do some config option settings, preferrably sooner rather than later. Perhaps as time goes on, I'll gain a better understanding of what to set where and how. josh _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Josh Boyer 2012-05-22T14:53:47 What is the earliest x86 64bit CPU we support? http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3798 <pre>So... what is it? I think the earliest is the AMD Opteron (2003). From a "earliest in each family" perspective, I think the answer is: AMD: AMD Opteron (2003). Intel: Intel Xeon (Nocona) (2004) VIA: VIA Nano (2008) Excluding Itanium (thank god), are there any other early x86 64bit CPUs that I'm missing or any that we explicitly no longer support? ~tom == Fedora Project _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Tom Callaway 2012-05-21T14:41:39 CONFIG_NR_CPUS http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3786 <pre> _today_ amd: 4sockets * 16cores = 64 intel: 4sockets * 10cores * 2threads = 80 _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Xose Vazquez Perez 2012-05-19T12:54:33 mount --move http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3785 <pre>I'm pretty sure that in 3.3.2-6.fc16.x86_64 this sequence worked: mkdir -p /tmp/testing cd /tmp/testing/ mkdir -p foo bar mount -t tmpfs tmpfs foo/ mount --move foo bar/ With 3.3.5-2.fc16.x86_64 the last step gives: mount: wrong fs type, bad option, bad superblock on /tmp/testing/foo, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Didn't test any kernels between those two. Is this a bug or feature? Didn't see anything is syslog. </pre> Norman Gaywood 2012-05-17T23:51:31 irc meeting minutes 2012-05-11 http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3783 <pre>====================================== #fedora-meeting: Fedora Kernel meeting ====================================== Meeting started by davej at 18:00:38 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2012-05-11/fedora_kernel_meeting.2012-05-11-18.00.log.html Meeting summary --------------- * auto-testing initiative. (davej, 18:02:52) * LINK: https://fedoraproject.org/wiki/KernelTestingInitiative (jwb, 18:10:32) * ACTION: create kernel-tests git repo on fedorahosted (davej, 18:12:51) Meeting ended at 18:57:25 UTC. Action Items ------------ * create kernel-tests git repo on fedorahosted People Present (lines said) --------------------------- * jforbes (73) * davej (40) * jwb (29) * nirik (7) * zodbot (3) * pjones (1) _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Dave Jones 2012-05-11T19:00:51 [PATCH] sunrpc: set CONFIG_SUNRPC_DEBUG=y in config.debug http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3779 <pre>This is quite handy for debugging but was recently made optional in mainline kernels since it shrinks the size of the rpc/nfs modules substantially if you turn it off. This patch turns it on in debug kernels. Should we also consider reenabling this in non-debug kernels? Signed-off-by: Jeff Layton &lt;jlayton&lt; at &gt;redhat.com&gt; --- config-debug | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/config-debug b/config-debug index 03964c6..955c0c7 100644 --- a/config-debug +++ b/config-debug &lt; at &gt;&lt; at &gt; -109,3 +109,4 &lt; at &gt;&lt; at &gt; CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=1024 # CONFIG_DEBUG_KMEMLEAK_TEST is not set CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y +CONFIG_SUNRPC_DEBUG=y </pre> Jeff Layton 2012-05-11T12:40:32 latest Rawhide Kernel in Koji http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3776 <pre>http://koji.fedoraproject.org/koji/buildinfo?buildID=318271 Missing kernel.i686 kernel.x86_64 in case there's some build problem </pre> Frank Murphy 2012-05-10T14:38:31 [patch f17 00/11] team: refresh to latest net-next http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3762 <pre>Refresh team driver co so it can work correctly with recent libteam version. All patches are in net-next tree David S. Miller (1): team: Stop using NLA_PUT*(). Jiri Pirko (10): team: add binary option type team: add loadbalance mode team: add support for per-port options team: add bool option type team: add user_linkup and user_linkup_enabled per-port option team: ab: walk through port list non-rcu team: add missed "statics" team: lb: let userspace care about port macs team: allow to enable/disable ports team: add per-port option for enabling/disabling ports drivers/net/team/Kconfig | 11 + drivers/net/team/Makefile | 1 + drivers/net/team/team.c | 523 +++++++++++++++++++++++------ drivers/net/team/team_mode_activebackup.c | 20 +- drivers/net/team/team_mode_loadbalance.c | 174 ++++++++++ drivers/net/team/team_mode_roundrobin.c | 2 +- 6 files changed, 621 insertions(+), 110 deletions(-) create mode 100644 drivers/net/team/team_mode_loadbalance.c </pre> Jiri Pirko 2012-05-04T15:29:40 [PATCH 0/7] NFS Client Bug Fixes. http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3752 <pre>This a set of 3.4 bug fixes that were recently posted and was suggested by the NFS maintainer we get into the Fedora kernels Rawhide already has these bug fixes but f17 and f16 do not. Fred Isaman (2): NFS: put open context on error in nfs_pagein_multi NFS: put open context on error in nfs_flush_multi Jan Kara (1): nfs: Enclose hostname in brackets when needed in nfs_do_root_mount Trond Myklebust (4): NFSv4: Ensure that the LOCK code sets exception-&gt;inode NFSv4: Ensure that we check lock exclusive/shared type against open modes NFS: Optimise away unnecessary setattrs for open(O_TRUNC); NFSv4: Fix open(O_TRUNC) and ftruncate() error handling fs/nfs/dir.c | 25 +++++++++++++++++++------ fs/nfs/inode.c | 4 ++-- fs/nfs/nfs4proc.c | 48 ++++++++++++++++++++++++++++++++++++++++-------- fs/nfs/read.c | 2 +- fs/nfs/super.c | 8 ++++++-- fs/nfs/write.c | 2 +- 6 files changed, 69 insertions(+), 20 deletions(-) </pre> Steve Dickson 2012-05-01T17:49:47 CCISS Support in FC16? http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3745 <pre>Upon upgrading from FC14 to FC16 this DL380-G4 cannot be booted from any of the FC16 kernels. Still boots successfully from the old FC14 kernel. The results when booting 3.1.0 and 3.3.2 are different. The results when booting 3.3.2-1.fc16.i686.PAE and 3.3.2-6.fc16.i686.PAE are identical.I followed the instructions on fedoraproject.org, modifying the kernel command line options to get debugging output. 3.3.2 - console output - both 3.3.2-1.fc16.i686.PAE and 3.3.2-6.fc16.i686.PAE -------------------------------------------------------------- ... [see attachment] Write protecting the kernel text: 5456k Write protecting the kernel read-only data: 2124k NX-protecting the kernel data: 4784K init[1] general protection ip:b771a419 sp:bffccc5c error:0 Kernel panic - not syncing: Attempting to kill init! ---------------------------------------------------------------------- At this point the system is locked up and there does not appear to be any way to retrieve any init.log file. See the attachment for a screen dump of the final bits of the console output. Because this computer is located remotely I don't have any way to access more output than that. All initramfs files for all kernels have the cciss driver, according to lsinitrd. Neverethless, the FC16 kernels fail to boot. 3.1.0 console output ----------------------------------------------------- ....[lots of output] dmesg | grep dracut &gt;&gt;&gt; very many screenshots [ I have no way to save the output to a file] The last 7 screens of this dmesg output are attached. From the emergency shell, the output of dmsetup ls --tree --&gt; No devices found blkid --&gt; no output blkid -c udev --&gt; no output I am not sure what the initramfs is doing, but it appears to have trouble finding the LVM/ext3 root filesystem. 2.6 Boot --------------------------------------------------- Boots normally. Some data: dmsetup ls --tree VolGroup00-LogVol01 (253:1) └─ (104:2) VolGroup00-LogVol00 (253:0) └─ (104:2) blkid /dev/cciss/c0d0p1: LABEL="/boot" UUID="c051ed89-7747-4756-bb8e-6f15ccfead88" SEC_TYPE="ext2" TYPE="ext3" /dev/dm-0: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/dm-1: TYPE="swap" /dev/cciss/c0d1p5: LABEL="/data1" UUID="c082e209-e3d9-4515-9327-e78fb434088a" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d1p6: LABEL="/data2" UUID="3882e8f8-817e-4a6a-ae36-febcabddfcd4" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2: LABEL="data2" UUID="57fe361b-0d73-4cc9-9592-cfc7c8fad00d" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p5: LABEL="/data3" UUID="5f079cb2-a086-4700-9b87-5d57e706dca8" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p6: LABEL="/data4" UUID="cfcf37a2-f2ff-4ff5-98c7-d4fcd40e7418" SEC_TYPE="ext2" TYPE="ext3" /dev/VolGroup00/LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/VolGroup00/LogVol01: TYPE="swap" /dev/mapper/VolGroup00-LogVol01: TYPE="swap" /dev/mapper/VolGroup00-LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d0p2: UUID="IC0t0N-WiTL-UQ7d-IsRD-w5Hz-91Pv-Big08T" TYPE="LVM2_member" blkid -c udev /dev/cciss/c0d0p1: LABEL="/boot" UUID="c051ed89-7747-4756-bb8e-6f15ccfead88" TYPE="ext3" /dev/cciss/c0d0p2: UUID="IC0t0N-WiTL-UQ7d-IsRD-w5Hz-91Pv-Big08T" TYPE="LVM2_member" /dev/cciss/c0d1p5: LABEL="/data1" UUID="c082e209-e3d9-4515-9327-e78fb434088a" TYPE="ext3" /dev/cciss/c0d1p6: LABEL="/data2" UUID="3882e8f8-817e-4a6a-ae36-febcabddfcd4" TYPE="ext3" /dev/cciss/c0d2: LABEL="data2" UUID="57fe361b-0d73-4cc9-9592-cfc7c8fad00d" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p5: LABEL="/data3" UUID="5f079cb2-a086-4700-9b87-5d57e706dca8" TYPE="ext3" /dev/cciss/c0d2p6: LABEL="/data4" UUID="cfcf37a2-f2ff-4ff5-98c7-d4fcd40e7418" TYPE="ext3" /dev/mapper/VolGroup00-LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" TYPE="ext3" /dev/mapper/VolGroup00-LogVol01: TYPE="swap" more /etc/fstab /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 LABEL=/data1 /d0 ext3 rw,acl 1 2 LABEL=/data2 /d1 ext3 defaults 1 2 LABEL=/data3 /d2 ext3 defaults 1 2 LABEL=/data4 /d3 ext3 defaults 1 2 Thanks! Jim _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> James Schatzman 2012-04-29T21:34:45 F15, F16 and F17 on the same kernel but with different patch sets? http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3743 <pre>Currently F15, f16 and f17 are on one and the same kernel but when you look at the git repo you'll see that those don't get the same patches. It looks like that most of the developers push to f17 and then let others apply the patches to f16 and f15 (if they are applied at all). It'll be great if those repos are synced and every future patch is applied to all three kernel. </pre> Joshua C. 2012-04-29T08:52:04 CCISS Support in FC16 http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3739 <pre>Apparently I got my wires crossed slightly. The results when booting 3.1.0 and 3.3.2 are different. So... I followed the instructions on fedoraproject.org, modifying the kernel command line options to get debugging output. 3.3.2 - console output -------------------------------------------------------------- ... [see attachment] Write protecting the kernel text: 5456k Write protecting the kernel read-only data: 2124k NX-protecting the kernel data: 4784K init[1] general protection ip:b771a419 sp:bffccc5c error:0 Kernel panic - not syncing: Attempting to kill init! ---------------------------------------------------------------------- At this point the system is locked up and there does not appear to be any way to retrieve any init.log file. See the attachment for a screen dump of the final bits of the console output. Because this computer is located remotely I don't have any way to access more output than that. 3.1.0 console output ----------------------------------------------------- ....[lots of output] dmesg | grep dracut &gt;&gt;&gt; very many screenshots [ I have no way to save the output to a file] The last 7 screens of this dmesg output are attached. From the emergency shell, the output of dmsetup ls --tree --&gt; No devices found blkid --&gt; no output blkid -c udev --&gt; no output 2.6 Boot --------------------------------------------------- Boots normally. Some data: dmsetup ls --tree VolGroup00-LogVol01 (253:1) └─ (104:2) VolGroup00-LogVol00 (253:0) └─ (104:2) blkid /dev/cciss/c0d0p1: LABEL="/boot" UUID="c051ed89-7747-4756-bb8e-6f15ccfead88" SEC_TYPE="ext2" TYPE="ext3" /dev/dm-0: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/dm-1: TYPE="swap" /dev/cciss/c0d1p5: LABEL="/data1" UUID="c082e209-e3d9-4515-9327-e78fb434088a" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d1p6: LABEL="/data2" UUID="3882e8f8-817e-4a6a-ae36-febcabddfcd4" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2: LABEL="data2" UUID="57fe361b-0d73-4cc9-9592-cfc7c8fad00d" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p5: LABEL="/data3" UUID="5f079cb2-a086-4700-9b87-5d57e706dca8" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p6: LABEL="/data4" UUID="cfcf37a2-f2ff-4ff5-98c7-d4fcd40e7418" SEC_TYPE="ext2" TYPE="ext3" /dev/VolGroup00/LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/VolGroup00/LogVol01: TYPE="swap" /dev/mapper/VolGroup00-LogVol01: TYPE="swap" /dev/mapper/VolGroup00-LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d0p2: UUID="IC0t0N-WiTL-UQ7d-IsRD-w5Hz-91Pv-Big08T" TYPE="LVM2_member" blkid -c udev /dev/cciss/c0d0p1: LABEL="/boot" UUID="c051ed89-7747-4756-bb8e-6f15ccfead88" TYPE="ext3" /dev/cciss/c0d0p2: UUID="IC0t0N-WiTL-UQ7d-IsRD-w5Hz-91Pv-Big08T" TYPE="LVM2_member" /dev/cciss/c0d1p5: LABEL="/data1" UUID="c082e209-e3d9-4515-9327-e78fb434088a" TYPE="ext3" /dev/cciss/c0d1p6: LABEL="/data2" UUID="3882e8f8-817e-4a6a-ae36-febcabddfcd4" TYPE="ext3" /dev/cciss/c0d2: LABEL="data2" UUID="57fe361b-0d73-4cc9-9592-cfc7c8fad00d" SEC_TYPE="ext2" TYPE="ext3" /dev/cciss/c0d2p5: LABEL="/data3" UUID="5f079cb2-a086-4700-9b87-5d57e706dca8" TYPE="ext3" /dev/cciss/c0d2p6: LABEL="/data4" UUID="cfcf37a2-f2ff-4ff5-98c7-d4fcd40e7418" TYPE="ext3" /dev/mapper/VolGroup00-LogVol00: UUID="8af89900-0449-40e8-952a-75b8ffa7a693" TYPE="ext3" /dev/mapper/VolGroup00-LogVol01: TYPE="swap" more /etc/fstab /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 LABEL=/data1 /d0 ext3 rw,acl 1 2 LABEL=/data2 /d1 ext3 defaults 1 2 LABEL=/data3 /d2 ext3 defaults 1 2 LABEL=/data4 /d3 ext3 defaults 1 2 Thanks! Jim _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> James Schatzman 2012-04-24T22:13:02 CCISS Support in FC16 http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3723 <pre>Can anyone tell me what kernel versions have support restored for CCISS SCSI controllers? After upgrading to FC16 with yum, my DL380 G4 no longer boots under either 3.1.0-7.fc16.i686 or 3.3.2-1-fc16.PAE kernels. Under the 3.1.0 kernel, dracut at least reports "dracut Warning: No root device /dev/VolGroup00/LogVol00 found". The 3.3.2 kernel reports only "Kernel panic - not syncing: Attempted to kill init!" which does not seem to be very informative to the non-kernel expert. Re-running "dracut -f" to rebuild the initramfs for either kernel does not help. No change in the behaviro is observed. II have seen bug report rhbz #754907 which may possibly be the same problem. This supposedly has been fixed but in what kernels? Thanks! Jim _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> James Schatzman 2012-04-23T13:25:31 kernel.git: add "version-release" tags? http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3717 <pre>0) Would it be possible to add tags to the kernel.git repository corresponding to the "%{VERSION}-%{RELEASE}" tags (ie, rpm querytags) of the kernel rpms (that have actually been released)? 1) Eg, checking out the current Fedora 16 kernel could be done with git checkout 3.3.2-1.fc16 instead of rpm -q kernel-3.3.2-1.fc16 --changelog | head git log -p origin/f16 | less [ grep on the string "Linux 3.3.2" ] [ copy a sha1sum ] git checkout 28b13140ec3375d59bac4f2d6bc336f7b8ed6fc7 2) Or would that require a lot of work for the people in charge of stuff like that? (3) This is not really a kernel.git specific thing. It just ran into this issue once again with the Fedora kernel rpms, because I happen to build those more often than other Fedora rpms.) Paul Bolle _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Paul Bolle 2012-04-21T16:25:55 Regression testing http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3712 <pre>As some of you have seen in our community meeting and minutes, we are working on actively testing the kernel builds. The short version is a series of regression tests which reside in either the kernel git tree and can be run with 'make tests' or possibly a control script in a kernel-tests subpackage. This will allow any user to run the regression tests against their running kernel on real hardware, and hopefully improve the test base considerably. In addition we will have autotest hooked up to do this plus more extensive testing. More details can be found at https://fedoraproject.org/wiki/KernelTestingInitiative So here is the part where we really want to get community involved. We have a wiki page created to list the regression tests that need to be written, and even sign up to write some if you are so inclined. We need your ideas for regression tests. Tests should be simple pass/fail checks. Tests against specific modules are allowed and encouraged. For users testing where they module is not loaded, the test will simply be skipped. Destructive testing is possible, though it will not be included in the standard test run (a user should know and explicitly sign up for a risk of data loss). Please take a look and add your ideas: https://fedoraproject.org/wiki/KernelRegressionTests Thanks, Justin _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Justin M. Forbes 2012-04-20T15:05:22 Rawhide kernels Changes? http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3710 <pre>Haven't been able to boot since: kernel-3.4.0-0.rc3.git0.1.fc18 Immediately after line showing removing RD, MD RAID activation Drops to a dracut shell. Novelties such as locate, dir don't exist. KVM Guests i386, x86_64 Have installed kernel-modules-extra, as a just in case. Looking at the changlogs for the last couple of kernels since, can't really make out anything substantial. Virt\real hard hasn't changed. </pre> Frank Murphy 2012-04-20T08:21:43 new kernel header file not being packaged in kernel-headers http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3704 <pre>Recently, I added a new upcall to mainline kernels and with that I added a new header file to describe the upcall/downcall format (include/linux/nfsd/cld.h). I've noticed though that that file is not being packaged in the kernel-headers package, even though the other files in the linux/nfsd dir are. Is there some master list that I need to add this file to? Or do I need to mark this file in some way to ensure that it gets included in kernel-headers? Thanks in advance, </pre> Jeff Layton 2012-04-16T14:24:47 Fedora Kernel Meeting 04-13-2012 Minutes http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3703 <pre>====================================== #fedora-meeting: Fedora Kernel Meeting ====================================== Meeting started by jforbes at 18:00:12 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2012-04-13/fedora-meeting.2012-04-13-18.00.log.html . Meeting summary --------------- * F15 (jforbes, 18:01:13) * Taking an exceptionally long time to get karma for F15 kernels * F16 (jforbes, 18:08:06) * F17 (jforbes, 18:14:54) * rawhide (jforbes, 18:17:44) * kernel-module-extras (jforbes, 18:21:31) * dlm module to be moved to kernel-module-extras (jforbes, 18:40:10) * open floor (jforbes, 18:56:31) Meeting ended at 18:58:50 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jforbes (57) * davej (47) * jwb (47) * swhiteho (46) * brunowolff_ (3) * zodbot (2) * pjones (2) * nirik (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Justin M. Forbes 2012-04-13T19:28:14 First 3.4 rc2 build is a debug build http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3699 <pre>Can we get a release build for the next rc2 build as a make up? _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Bruno Wolff III 2012-04-09T17:07:21 [PATCH] SELinux: apply a different permission to ptrace a child vsnon-child http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3696 <pre>Some applications, like gdb, are able to ptrace both children or other completely unrelated tasks. We would like to be able to discern these two things and to be able to allow gdb to ptrace it's children, but not to be able to ptrace unrelated tasks for security reasons. Upstream is a bit weary of this patch as it may be incomplete. They are not fundamentally opposed to the patch, I was just ask to see if I could flush out any needed refinement in Fedora where we already had the problem. We may find that we need to emulate the YAMA non-child registration module in order to completely deal with 'normal' ptrace on a system. At the moment however, this patch will at least let us get gdb working for many users in Fedora (See fedora-devel-list for a discussion of the current issues people are complaining about in F17 without this) --- security/selinux/hooks.c | 38 +++++++++++++++++++++++++++++++++++ security/selinux/include/classmap.h | 2 +- security/selinux/include/security.h | 2 ++ security/selinux/selinuxfs.c | 3 ++- security/selinux/ss/services.c | 3 +++ 5 files changed, 46 insertions(+), 2 deletions(-) diff --git a/security/selinux/hooks.c b/security/selinux/hooks.c index 1a4acf4..b226f26 100644 --- a/security/selinux/hooks.c +++ b/security/selinux/hooks.c &lt; at &gt;&lt; at &gt; -1805,6 +1805,39 &lt; at &gt;&lt; at &gt; static inline u32 open_file_to_av(struct file *file) /* Hook functions begin here. */ +/** + * task_is_descendant - walk up a process family tree looking for a match + * &lt; at &gt;parent: the process to compare against while walking up from child + * &lt; at &gt;child: the process to start from while looking upwards for parent + * + * Returns 1 if child is a descendant of parent, 0 if not. + */ +static int task_is_descendant(struct task_struct *parent, + struct task_struct *child) +{ +int rc = 0; +struct task_struct *walker = child; + +if (!parent || !child) +return 0; + +rcu_read_lock(); +if (!thread_group_leader(parent)) +parent = rcu_dereference(parent-&gt;group_leader); +while (walker-&gt;pid &gt; 0) { +if (!thread_group_leader(walker)) +walker = rcu_dereference(walker-&gt;group_leader); +if (walker == parent) { +rc = 1; +break; +} +walker = rcu_dereference(walker-&gt;real_parent); +} +rcu_read_unlock(); + +return rc; +} + static int selinux_ptrace_access_check(struct task_struct *child, unsigned int mode) { &lt; at &gt;&lt; at &gt; -1820,6 +1853,9 &lt; at &gt;&lt; at &gt; static int selinux_ptrace_access_check(struct task_struct *child, return avc_has_perm(sid, csid, SECCLASS_FILE, FILE__READ, NULL); } + +if (selinux_policycap_ptrace_child &amp;&amp; task_is_descendant(current, child)) +return current_has_perm(child, PROCESS__PTRACE_CHILD); return current_has_perm(child, PROCESS__PTRACE); } &lt; at &gt;&lt; at &gt; -1831,6 +1867,8 &lt; at &gt;&lt; at &gt; static int selinux_ptrace_traceme(struct task_struct *parent) if (rc) return rc; +if (selinux_policycap_ptrace_child &amp;&amp; task_is_descendant(parent, current)) +return task_has_perm(parent, current, PROCESS__PTRACE_CHILD); return task_has_perm(parent, current, PROCESS__PTRACE); } diff --git a/security/selinux/include/classmap.h b/security/selinux/include/classmap.h index 39e678c..72c08b9 100644 --- a/security/selinux/include/classmap.h +++ b/security/selinux/include/classmap.h &lt; at &gt;&lt; at &gt; -29,7 +29,7 &lt; at &gt;&lt; at &gt; struct security_class_mapping secclass_map[] = { "getattr", "setexec", "setfscreate", "noatsecure", "siginh", "setrlimit", "rlimitinh", "dyntransition", "setcurrent", "execmem", "execstack", "execheap", "setkeycreate", - "setsockcreate", NULL } }, + "setsockcreate", "ptrace_child", NULL } }, { "system", { "ipc_info", "syslog_read", "syslog_mod", "syslog_console", "module_request", NULL } }, diff --git a/security/selinux/include/security.h b/security/selinux/include/security.h index dde2005..ac14b0a 100644 --- a/security/selinux/include/security.h +++ b/security/selinux/include/security.h &lt; at &gt;&lt; at &gt; -68,12 +68,14 &lt; at &gt;&lt; at &gt; extern int selinux_enabled; enum { POLICYDB_CAPABILITY_NETPEER, POLICYDB_CAPABILITY_OPENPERM, +POLICYDB_CAPABILITY_PTRACE_CHILD, __POLICYDB_CAPABILITY_MAX }; #define POLICYDB_CAPABILITY_MAX (__POLICYDB_CAPABILITY_MAX - 1) extern int selinux_policycap_netpeer; extern int selinux_policycap_openperm; +extern int selinux_policycap_ptrace_child; /* * type_datum properties diff --git a/security/selinux/selinuxfs.c b/security/selinux/selinuxfs.c index 4e93f9e..3379765 100644 --- a/security/selinux/selinuxfs.c +++ b/security/selinux/selinuxfs.c &lt; at &gt;&lt; at &gt; -44,7 +44,8 &lt; at &gt;&lt; at &gt; /* Policy capability filenames */ static char *policycap_names[] = { "network_peer_controls", -"open_perms" +"open_perms", +"ptrace_child", }; unsigned int selinux_checkreqprot = CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE; diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c index 9b7e7ed..4d12a6e 100644 --- a/security/selinux/ss/services.c +++ b/security/selinux/ss/services.c &lt; at &gt;&lt; at &gt; -72,6 +72,7 &lt; at &gt;&lt; at &gt; int selinux_policycap_netpeer; int selinux_policycap_openperm; +int selinux_policycap_ptrace_child; static DEFINE_RWLOCK(policy_rwlock); &lt; at &gt;&lt; at &gt; -1812,6 +1813,8 &lt; at &gt;&lt; at &gt; static void security_load_policycaps(void) POLICYDB_CAPABILITY_NETPEER); selinux_policycap_openperm = ebitmap_get_bit(&amp;policydb.policycaps, POLICYDB_CAPABILITY_OPENPERM); +selinux_policycap_ptrace_child = ebitmap_get_bit(&amp;policydb.policycaps, + POLICYDB_CAPABILITY_PTRACE_CHILD); } static int security_preserve_bools(struct policydb *p); _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Eric Paris 2012-04-09T13:59:18 how to build carl9170 firmware http://comments.gmane.org/gmane.linux.redhat.fedora.kernel/3693 <pre>Hi, after a discussion with jwb and linvile on #fedora-kernel I did some experiments how could be the carl9170 firmware [1] built using the existing tools (dhowell's cross-gcc [2]). And the result is that it is feasible. See first patch for proof of concept using sh4-linux-gnu toolchain and second patch for proposed solution after we get the sh-linux-gnu toolchain (https://bugzilla.redhat.com/show_bug.cgi?id=766166#c12). Dan [1] http://linuxwireless.org/en/users/Drivers/carl9170 [2] http://koji.fedoraproject.org/koji/packageinfo?packageID=13624 _______________________________________________ kernel mailing list kernel&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel</pre> Dan Horák 2012-04-06T09:13:32 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.redhat.fedora.kernel