17:00 <jsalisbury> #startmeeting
17:00 <meetingology> Meeting started Tue May 21 17:00:38 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00 <meetingology> 
17:00 <meetingology> 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 <jsalisbury> ##
17:00 <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
17:00 <jsalisbury> ##
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring
17:00 <jsalisbury> # Meeting Etiquette
17:00 <jsalisbury> #
17:00 <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
17:00 <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
17:00 <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
17:00 <bjf> o/
17:00 <ppisati> o/
17:00 <rtg_> o/
17:00 <cking> o/
17:00 <henrix> o/
17:00 <sforshee> o/
17:01 <jsalisbury> [TOPIC] ARM Status (ppisati)
17:01 <ppisati> Q/master: lp1176977 ("XFS instability on armhf under load") - working with
17:01 <ppisati> upstream on this one: i already backported a fix that turn the vmalloc() exhaustion
17:01 <ppisati> and fs shutdown to an -ENOSPC error, and this second error seems to be triggered
17:01 <ppisati> by the tiny fs used in these tests (~2GB). Still working to get it
17:01 <ppisati> properly fixed.
17:01 <ppisati> R/master: lp1171582("[highbank] hvc0 getty causes random hangs") -
17:01 <ppisati> the jtag console has a 1-char producer-consumer buffer and if there's no
17:01 <ppisati> real hw attached to the board, any subsequent write turn into an endless loop
17:01 <ppisati> waiting for a consumer. The situation is worsened by the fact
17:01 <ppisati> that before writing to this register a tty spinlocked is taken, and
17:02 <ppisati> any subsequent tentative to pick this spinlock makes the thread hang -
17:02 <ppisati> got a confirmation of the problem, some info about the hw, and i'm working on this.
17:02 <ppisati> ..
17:02 <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
17:02 <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
17:02 <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
17:02 <jsalisbury> ..
17:02 <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
17:02 <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
17:02 <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-saucy/canonical-kernel-distro-team.html
17:02 <ogasawara> The burn down charts have not yet been reset for 13.10, so disregard the
17:02 <ogasawara> second link posted abovefor now.  I'll be cleaning up and adding work
17:02 <ogasawara> items for 13.10 so that the +upcomingwork link will be more accurate.
17:02 <ogasawara> Next week I'll have the usual nag table available.
17:02 <ogasawara> ..
17:03 <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
17:03 <ogasawara> For now, we'll plan on targetting the v3.10 kernel for Saucy but will
17:03 <ogasawara> strongly re-evaluate a move to v3.11 in the coming months.  We've just
17:03 <ogasawara> rebased Saucy to v3.10-rc2 and are still cleaning up some of the
17:03 <ogasawara> carnage.  I don't anticipate we'll upload until a later -rc which will
17:03 <ogasawara> hopefully provide more stability.
17:03 <ogasawara> Importand upcoming dates:
17:03 <ogasawara> Thurs June 20 - Alpha 1 (opt in)
17:03 <ogasawara> ..
17:03 <jsalisbury> [TOPIC] Status: CVE's (sconklin)
17:04 <sconklin> == 2013-05-21 (28 days) ==
17:04 <sconklin> Currently we have 63 CVEs on our radar, with 8 CVEs added and 17 CVEs retired in the last 28 days.
17:04 <sconklin> See the CVE matrix for the current list:
17:04 <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
17:04 <sconklin> Overall the backlog has decreased slightly this week:
17:04 <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
17:04 <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
17:04 <sconklin> ..
17:04 <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Oneiric/Lucid/Hardy (bjf/henrix/sconklin)
17:04 <sconklin> Support for Oneiric and Hardy expired on May 9th.
17:04 <sconklin> Status for the main kernels, until today (May. 21):
17:04 <sconklin> *   Lucid - In Testing;
17:04 <sconklin> * Precise - In Testing; 2 upstream releases;
17:04 <sconklin> * Quantal - In Testing; 2 upstream releases;
17:04 <sconklin> * Raring  - In Testing; 3 upstream releases;
17:04 <sconklin> Current opened tracking bugs details:
17:04 <sconklin> * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
17:04 <sconklin> For SRUs, SRU report is a good source of information:
17:04 <sconklin> * http://people.canonical.com/~kernel/reports/sru-report.html
17:04 <sconklin> Future stable cadence cycles:
17:04 <sconklin> * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
17:04 <sconklin> ..
17:05 <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
17:05 <jsalisbury> Thanks everyone
17:05 <jsalisbury> #endmeeting