#title #ubuntu-meeting Meeting Meeting started by jsalisbury at 17:00:36 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-12-13-17.00.log.html . == Meeting summary == ''LINK:'' https://wiki.ubuntu.com/KernelTeam/Meeting (jsalisbury, 17:00:36) ''LINK:'' https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise (jsalisbury, 17:00:37) *ARM Status (ppisati) *Release Metrics and Incoming Bugs (jsalisbury) ''LINK:'' http://people.canonical.com/~kernel/reports/kt-meeting.txt (jsalisbury, 17:01:20) *Milestone Targeted Work Items (ogasawara) ''LINK:'' http://status.ubuntu.com/ubuntu-precise/canonical-kernel-team-precise-alpha-2.html (ogasawara, 17:01:59) *Blueprint: hardware-p-kernel-power-management (cking) *Status: Precise Development Kernel (ogasawara) *Status: CVE's (apw) ''LINK:'' http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt (apw, 17:04:29) *Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton) *Hardware Certification - Testing Pools (brendand) ''LINK:'' https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AphFraZYTghddElqTHl3NmZsWXVDYkMxcE5zX3EtR0E&hl=en_US#gid=0 (brendand, 17:08:41) *Open Discussion or Questions? Raise your hand to be recognized (o/) Meeting ended at 17:25:39 UTC. == Votes == == Action items == * (none) == People present (lines said) == * apw (39) * bjf (32) * jsalisbury (30) * brendand (30) * ogasawara (21) * cking (16) * ubottu (10) * tgardner (4) * ppisati (3) * meetingology (3) == Full Log == 17:00:36 #startmeeting 17:00:36 Meeting started Tue Dec 13 17:00:36 2011 UTC. The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. 17:00:36 17:00:36 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 17:00:36 ## 17:00:36 ## This is the Ubuntu Kernel Team weekly status meeting. 17:00:36 ## 17:00:36 [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting 17:00:37 [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise 17:00:39 # Meeting Etiquette 17:00:41 # 17:00:43 # NOTE: '..' indicates that you are finished with your input. 17:00:45 # 'o/' indicates you have something to add (please wait until you are recognized) 17:01:00 [TOPIC] ARM Status (ppisati) 17:01:02 P/omap4: a new kernel (3.2.0-1402.2) based off 3.2 (Ubuntu-3.2.0-3.9) has been released, while a new TI BSP + 3.2-rc5 is in the pipe. 17:01:05 SRU kernels: nothing to report. 17:01:08 .. 17:01:20 [TOPIC] Release Metrics and Incoming Bugs (jsalisbury) 17:01:20 [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt 17:01:39 Just adding link this week, instead of posting all data. 17:01:44 .. 17:01:55 [TOPIC] Milestone Targeted Work Items (ogasawara) 17:01:59 [LINK] http://status.ubuntu.com/ubuntu-precise/canonical-kernel-team-precise-alpha-2.html 17:02:00 || apw || hardware-p-kernel-boot || 1 work item || 17:02:00 || || hardware-p-kernel-config-review || 4 work items || 17:02:00 || || hardware-p-kernel-delta-review || 4 work items || 17:02:00 || || foundations-p-ipv6 || 1 work item || 17:02:00 || cking || hardware-p-kernel-delta-review || 1 work item || 17:02:02 || jsalisbury || other-p-bug-workflows || 1 work item || 17:02:04 || ogasawara || hardware-p-kernel-version-and-flavors || 1 work item || 17:02:06 || || hardware-p-kernel-config-review || 21 work items|| 17:02:08 || tgardner || hardware-p-kernel-version-and-flavors || 1 work item || 17:02:10 || || hardware-p-kernel-delta-review || 1 work item || 17:02:12 If your name is in the above table, please review your Alpha-2 work items. Note that Alpha-2 is Thurs Feb 2. 17:02:15 .. 17:02:29 [TOPIC] Blueprint: hardware-p-kernel-power-management (cking) 17:02:32 Power Management: 17:02:32 * Re-run power.d readahead and journal-commit tests on non-idle 17:02:33 user application scenerios. 17:02:33 * Measure mouse power consumption, different rates + devices: 17:02:33 http://zinc.canonical.com/~cking/power-benchmarking/mouse-movement 17:02:33 * Complete PowerTop good/bad results: 17:02:35 http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad-recommendations 17:02:37 * Measure backlight levels power traits: 17:02:39 http://zinc.canonical.com/~cking/power-benchmarking/backlight-non-linearity 17:02:41 * More extensive 32 vs 64 bit power comparisons (in progress) 17:02:43 * Compare UEFI vs BIOS firmware (in progress) 17:02:45 * Complete pm-utils measurements: 17:02:49 http://zinc.canonical.com/~cking/power-benchmarking/pm-utils-results 17:02:51 * Crowd-sourcing pm-utils extra tweaks, CALL FOR TESTING: 17:02:53 https://wiki.ubuntu.com/Kernel/PowerManagementPMUtils 17:02:55 .. 17:03:21 [TOPIC] Status: Precise Development Kernel (ogasawara) 17:03:24 We have uploaded the 3.2.0-4.10 Ubuntu kernel which is based on latest upstream v3.2-rc5 kernel. Additionally, after yesterday's Tech Board discussion around the i386 non-pae flavor, it was decided to continue carrying this flavor for 12.04 and then drop it in 12.10. The installer will also be switched to default to the pae flavor for i386. 17:03:37 Important Upcoming Dates: 17:03:37 * Thurs Feb 2 - Alpha 2 (~7 weeks) 17:03:38 .. 17:04:06 [TOPIC] Status: CVE's (apw) 17:04:09 CVE-2010-4251 CVE-2010-4805 CVE-2011-1082 CVE-2011-1083: epoll DOS -- fix incomplete, referred back to Security for review 17:04:11 The socket implementation in net/core/sock.c in the Linux kernel before 2.6.34 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service (memory consumption) by sending a large amount of network traffic, as demonstrated by netperf UDP tests. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4251) 17:04:11 CVE-2011-1747: agp ioctl memory DOS -- no upstream fix as yet 17:04:12 The socket implementation in net/core/sock.c in the Linux kernel before 2.6.35 does not properly manage a backlog of received packets, which allows remote attackers to cause a denial of service by sending a large amount of network traffic, related to the sk_add_backlog function and the sk_rmem_alloc socket field. NOTE: this vulnerability exists because of an incomplete fix for... (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4805) 17:04:13 fs/eventpoll.c in the Linux kernel before 2.6.38 places epoll file descriptors within other epoll data structures without properly checking for (1) closed loops or (2) deep chains, which allows local users to cause a denial of service (deadlock or stack memory consumption) via a crafted application that makes epoll_create and epoll_ctl system calls. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1082) 17:04:13 CVE-2011-3347: be2net non-member vlan DOS -- cannot identify upstream fix 17:04:15 The epoll implementation in the Linux kernel 2.6.37.2 and earlier does not properly traverse a tree of epoll file descriptors, which allows local users to cause a denial of service (CPU consumption) via a crafted application that makes epoll_create and epoll_ctl system calls. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1083) 17:04:15 CVE-2011-3638: ext4 extent split -- upstream fix identified, pending application 17:04:16 The agp subsystem in the Linux kernel 2.6.38.5 and earlier does not properly restrict memory allocation by the (1) AGPIOC_RESERVE and (2) AGPIOC_ALLOCATE ioctls, which allows local users to cause a denial of service (memory consumption) by making many calls to these ioctls. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1747) 17:04:17 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3347) 17:04:17 CVE-2011-4112: pktgen bridge panic -- redhat is withdrawing the CVE 17:04:18 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3638) 17:04:19 CVE-2011-4131: nfs4 ACL oops -- fix is still iterating upstream, pending 17:04:19 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4112) 17:04:21 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4131) 17:04:21 CVE-2011-4347: kvm kvm_vm_ioctl_assign_device crashes -- no upsteam fix as yet 17:04:22 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4347) 17:04:23 17:04:25 === CVE Metrics === 17:04:27 17:04:29 [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt 17:04:31 17:04:33 Currently open CVEs for each supported branch: 17:04:35 17:04:37 || Package || Open || 17:04:39 || || || 17:04:41 || linux Hardy || 10 (-1) || 17:04:43 || linux Lucid || 7 (-1) || 17:04:45 || linux Maverick || 7 (-1) || 17:04:47 || linux Natty || 7 (-1) || 17:04:49 || linux Oneiric || 5 || 17:04:51 || linux Precise || 5 || 17:04:53 || linux-ec2 Lucid || 7 (-1) || 17:04:55 || linux-fsl-imx51 Lucid || 7 (-1) || 17:04:57 || linux-mvl-dove Lucid || 7 (-1) || 17:05:00 || linux-mvl-dove Maverick || 7 (-1) || 17:05:01 || linux-ti-omap4 Maverick || 7 (-1) || 17:05:03 || linux-ti-omap4 Natty || 7 (-1) || 17:05:05 || linux-ti-omap4 Oneiric || 5 || 17:05:08 || linux-ti-omap4 Precise || 5 || 17:05:09 || linux-lts-backport-maverick Lucid || 7 (-1) || 17:05:12 || linux-lts-backport-natty Lucid || 7 (-1) || 17:05:13 || linux-lts-backport-oneiric Lucid || 5 || 17:05:16 17:05:17 We only have one open CVE with an upstream fix currently. The remainder await fixes from upstream. 17:05:20 17:05:21 .. 17:05:23 (bah, will drop the CVE- prefix for future updates.) .. 17:05:45 [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton) 17:05:52 Many of the kernels in -proposed were quickly verified and went into 17:05:54 regression testing early. This week is mostly about finishing up the 17:05:56 stragglers. A new Oneiric has been prep'd and uploaded. We'll just have 17:05:58 to see if we can get it verified and regression tested before the 17:06:00 dead week of Christmas. 17:06:02 17:06:04 Here is the status for the main kernels, until today (13/12): 17:06:06 17:06:08 * Hardy - 2.6.24-30.97 17:06:10 * On holiday 17:06:12 17:06:14 * Lucid - 2.6.32-36.79 17:06:16 * Regression testing in progress. 17:06:18 17:06:20 * Maverick - 2.6.35-31.63 17:06:22 * On holiday 17:06:24 17:06:26 * Natty - 2.6.38-13.53 17:06:28 * Regression testing in progress. 17:06:30 17:06:32 * Oneiric - 3.0.0-14.23 17:06:34 * Prep'd and trying to reach -proposed 17:06:36 17:06:38 Current opened tracking bugs details: 17:06:40 * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html 17:06:42 17:06:44 For SRUs, SRU report is a good source of information: 17:06:46 * http://people.canonical.com/~kernel/reports/sru-report.html 17:06:48 17:06:50 Future stable cadence cycles: 17:06:52 * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock 17:06:54 .. 17:07:13 [TOPIC] Hardware Certification - Testing Pools (brendand) 17:07:18 hi 17:07:39 let me do this gradually 17:07:41 As part of the SRU workflow the hardware certification team tests the -proposed kernel on as many certified systems as possible. 17:07:41 As the number of certified systems for each release has grown, getting full coverage has become more and more difficult. 17:07:58 To allow us to reduce the number of systems tested we have devised a system of 'testing pools'. 17:07:58 This takes advantage of a system which stores details of the certified hardware including it constituent components to provide as broad a component coverage as possible. 17:08:14 Initially the system ensured that at least one instance of each piece of hardware (as identified by PCI Id's) was present in the testing pool. 17:08:14 This turned out not to fulfill the goal of the system since we still ended up with needing almost all the systems we had to provide full coverage (e.g. 165 systems certified for Natty gave a testing pool of 158) 17:08:41 We made a first effort at reducing the size of the pools by considering only components of particular categories to be 'important'. A list of these was sent to the kernel-team mailing list. 17:08:41 https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AphFraZYTghddElqTHl3NmZsWXVDYkMxcE5zX3EtR0E&hl=en_US#gid=0 17:09:03 These give us testing pools of ~50 systems. However we are not happy yet with the coverage. We need feedback on which components need to be added in. 17:09:21 The criteria used should be: how likely is it that a bug could occur in just a subset of the components of this category? A good example is the category 'Display Controller/VGA Compatible Controller' which we do cover already. We know for a fact that bugs will be specific to particular makes of graphics card. Same for CPUs ('Processor' category) 17:10:01 We really need feedback on this 17:10:41 ... 17:11:20 brendand, This will all be documented in the meeting minutes. It would be good if you could also follow up with an email to the kernel-team mailing list. 17:12:01 [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/) 17:12:09 brendand: Do you have a revised list which has all the possible components you want us to review to consider adding back in? Also, what # are you looking for to satify coverage? 17:12:53 ogasawara - if you can access that link then all the ones marked 'x' are not considered at the moment 17:13:27 we have no fixed number to reach 17:13:41 brendand, what is the max number of machines that you can cover ? 17:14:14 tgardner - it seems to be about 90, realistically speaking. something like that. 17:14:21 ack 17:14:51 i would prefer for now to take each component category on it's own merits' 17:15:16 rather than considering how many extra systems it adds. we (the hwcert team) can worry about managing that 17:15:40 i had a question to pose, as a bit of a thought experiment 17:16:14 Could a bug affect only a subset of device of the category 'Bridge/PCI bridge'? 17:16:48 brendand, likely, but its more likely to be BIOS specific 17:17:01 if there is more than one different piece of h/w in any category it is possible to get different results from each 17:17:33 however, we have way fewer problems with PCI bridges. 17:17:37 apw - yes, definitely *possible*. 17:18:25 actually the point of that question was to illustrate the line of thinking that needs to be taken to evaluate this list of component categories 17:18:59 between tgardner and apw that's the kind of critique of the list i'm looking for 17:19:25 thanks 17:19:54 Any Open Discussion comments? 17:19:57 one last thing. i'm not sure is that link public. anyone who can't get access please let me know and i'll sort something out 17:20:49 If no other comments, then going once 17:20:54 brendand: how do you want feedback, maybe a "feedback" column, and we'll add X's to categories we think should be added back? 17:21:25 ogasawara - i'm arranging for everyone to have edit rights and i'll add a feedback column 17:22:07 brendand: let us know when it's ready for editing. I'm sure a few of us can just a quick pass off and tick the ones we want. 17:22:22 .. 17:22:46 brendand, any other comments? 17:23:30 yeah, if any of the categories don't make sense to you, contact me about it 17:23:43 i'll send the link to the kernel-team list 17:24:25 brendand, dot dot then ? 17:24:28 .. 17:24:48 Any other open discussions or questions? 17:25:22 Last call 17:25:39 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/AlanBell/mootbot)