Archive for May, 2013

Joseph Salisbury

Kernel Team Meeting Minutes – May 28, 2013

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20130528 Meeting Agenda


ARM Status

Q/master: lp1176977 (“XFS instability on armhf under load”) – cherry picked two
more patches that address the free space fragmentation: the resulting kernel
passes all tests so far, i’m waiting for user feedback and one last batch of
tests.
*/highbank: lp1182637(“cpu_offlining fails to run on ARM”) – all the highbanks kernel that
we released so far are affected by this – basically, you can offline a cpu but
when you try to put it back, reinsetion fails and the only way to get the cpu back
is to reboot. Debugged till the point the cpu is plugged back, but it never really
starts and pick up the idle thread – i’ll probably need to do a comparison
between the boot environment (when the cpu are added to the system via the same
mechanism) and this scenario.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

I’m still working on cleaning up our team’s set of work items and
getting monthly goals properly refelcted in the blueprints.


Status: Saucy Development Kernel

Our Saucy unstable branch has been rebased to the latest v3.10-rc3
upstream kernel. Saucy master-next is currently at v3.9.3. I
anticipate we’ll cut over to v3.10 around the -rc4 time frame.
On the phablet side, we now have Ubuntu kernels in the archive for the
Nexus 4, 7, 10, and Galaxy Nexus devices. We also anticipate an
AppArmor pull request next week from the security team to get the latest
AppArmor patches into these kernels.
Important upcoming dates:
Thurs June 20 – Alpha 1 (opt in)


Status: CVE’s

== 2013-05-28 (7 days) ==
Currently we have 63 CVEs on our radar, with 0 CVEs added and 0 CVEs retired in the last week.
See the CVE matrix for the current list:

  • http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html

    Overall the backlog has decreased slightly this week:

  • http://people.canonical.com/~kernel/status/cve-metrics.txt

  • http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt


Status: Stable, Security, and Bugfix Kernel Updates – Raring/Quantal/Precise/Lucid/Hardy

Status for the main kernels, until today (May. 28):

  • Lucid – In Prep;
  • Precise – In Prep;
  • Quantal – In Prep;
  • Raring – In Prep;
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html

    Future stable cadence cycles:

  • https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock


Open Discussion or Questions? Raise your hand to be recognized

No open discussions.

Joseph Salisbury

Kernel Team Meeting Minutes – May 21, 2013

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20130521 Meeting Agenda


ARM Status

Q/master: lp1176977 (“XFS instability on armhf under load”) – working with
upstream on this one: i already backported a fix that turn the vmalloc() exhaustion
and fs shutdown to an -ENOSPC error, and this second error seems to be triggered
by the tiny fs used in these tests (~2GB). Still working to get it
properly fixed.
R/master: lp1171582(“[highbank] hvc0 getty causes random hangs”) -
the jtag console has a 1-char producer-consumer buffer and if there’s no
real hw attached to the board, any subsequent write turn into an endless loop
waiting for a consumer. The situation is worsened by the fact
that before writing to this register a tty spinlocked is taken, and
any subsequent tentative to pick this spinlock makes the thread hang -
got a confirmation of the problem, some info about the hw, and i’m working on this.


Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:

  • http://people.canonical.com/~kernel/reports/kt-meeting.txt


Milestone Targeted Work Items

The burn down charts have not yet been reset for 13.10, so disregard the
second link posted abovefor now. I’ll be cleaning up and adding work
items for 13.10 so that the +upcomingwork link will be more accurate.
Next week I’ll have the usual nag table available.


Status: Saucy Development Kernel

For now, we’ll plan on targetting the v3.10 kernel for Saucy but will
strongly re-evaluate a move to v3.11 in the coming months. We’ve just
rebased Saucy to v3.10-rc2 and are still cleaning up some of the
carnage. I don’t anticipate we’ll upload until a later -rc which will
hopefully provide more stability.
Importand upcoming dates:
Thurs June 20 – Alpha 1 (opt in)


Status: CVE’s

== 2013-05-21 (28 days) ==
Currently we have 63 CVEs on our radar, with 8 CVEs added and 17 CVEs retired in the last 28 days.
See the CVE matrix for the current list:

  • http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html

    Overall the backlog has decreased slightly this week:

  • http://people.canonical.com/~kernel/status/cve-metrics.txt

  • http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt


Status: Stable, Security, and Bugfix Kernel Updates – Raring/Quantal/Precise/Oneiric/Lucid/Hardy

Support for Oneiric and Hardy expired on May 9th.
Status for the main kernels, until today (May. 21):

  • Lucid – In Testing;
  • Precise – In Testing; 2 upstream releases;
  • Quantal – In Testing; 2 upstream releases;
  • Raring – In Testing; 3 upstream releases;
    Current opened tracking bugs details:
  • http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

    For SRUs, SRU report is a good source of information:

  • http://people.canonical.com/~kernel/reports/sru-report.html

    Future stable cadence cycles:

  • https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock


Open Discussion or Questions? Raise your hand to be recognized

Thanks everyone