[06:20] <icey> I'm currently testing a fairly small patch to my Artful kernel, the patch is proposed against upstream Linux but I suspect won't make it into the Artful kernel at release, assuming it works (in which case I'll +1 on the kernel ML as well), how hard would it be to get this patch added for Artful: https://patchwork.kernel.org/patch/9842347/
[06:31] <tjaalton> do we handle v4.10.x.y stable releases?
[06:31] <tjaalton> or whatever the version should be
[06:31] <tjaalton> .17 is the last one provided by stable@
[06:36] <tjaalton> too bad "[PATCH] drm/i915: Do not drop pagetables when empty" never was applied to v4.10.17.x if such a thing exists
[06:46] <smb> tjaalton, afaik nobody started a follow-up longterm for 4.10. So anything that should go into zesty has to be individually sent to kt-ml
[06:46] <smb> which rex tsai did recently
[06:47] <tjaalton> smb: ok, so -cktNN releases for non-lts kernels are no longer happening?
[06:47] <tjaalton> yeah good that the patch is now on the queue
[06:48] <smb> tjaalton, no, unfortunately too many other things
[06:48] <tjaalton> ok
[06:48] <tjaalton> I only found out about the bug today :/
[06:48] <tjaalton> my skl desktop is still on xenial
[06:49] <smb> Yeah, I am rather conservative there as well
[08:07] <icey> what's the policy for integrating kernel patches that enable hardware but aren't yet merged upstream?
[08:39] <apw> icey, we prefer to see things whihc are being discussed upstream and making progress there over things that are flat rejecte
[08:40] <icey> apw: seems to be still under discussion, it's just quite new: https://patchwork.kernel.org/patch/9842347/
[08:43] <ricotz> apw, hi :), what is up with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772 ?
[08:43] <ricotz> the upstreamed patches are available since over month and included in 4.4.74 which still hasnt got into a 4.4 package release, this still breaks the i386 tests suite of libreoffice and the currently included patches for CVE-2017-1000364 are not sufficient
[08:43] <apw> icey, one of those sorts of quirks would normally be pretty easy to accept as the only person you can screw is you
[08:44] <icey> apw: I'm building it into a custom kernel now, I just don't want to have to d that regularly ;-)
[08:44] <apw> ricotz, as far as i know those are the mm fixes on top of the fixes for the stackclash CVE
[08:44] <apw> ricotz, and those i believe are out, they went out as an emergency kernel in xenial iirc
[08:45] <ricotz> apw, I saw those but those are not sufficient
[08:45] <ricotz> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y&id=4b359430674caa2c98d0049a6941f157d2a33741 and https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y&id=1f2284fac2180d7a9442c796d9755e3ce7ab0bd9 are required
[08:53] <apw> ricotz, both of those are applied in 4.4.0-83.106 and -87 is in -security
[08:54] <apw> though those are the original two commits so i assume those are not the ones you intended
[08:57] <icey> apw: that patch works :)
[08:59] <ricotz> apw, hmm, I see, not sure then which are the proper fixes, still the java crash is happening on i386 with -87
[08:59] <apw> icey, so submit a bug against linux 'ubuntu-bug linux' and write it up in there, then send the patch to kernel-team@
[08:59] <ricotz> apw, for reference https://launchpad.net/~ricotz/+archive/ubuntu/red/+build/13178350
[09:04] <apw> ricotz, have you tried -88
[09:06] <ricotz> apw, no
[09:07] <icey> apw should I attach the patch even though the bug report includes a link to the patch on patchwork.kernel.org?
[09:08] <apw> icey, not necessary
[09:08] <icey> apw: should I send an email at all, or just link the bug (https://launchpad.net/ubuntu/+source/linux/+bug/1708120)?
[09:09] <apw> i would send the patch requesting the SRU to kernel-team@
[09:09] <icey> apw: should it be an SRU for artful (unreleased) ?
[09:22] <apw> icey, are you runnig artful, if so then just leave out the SRU bit of the wording as we don't call it that for devel
[09:22] <apw> ricotz, do we know if this explods on artful too ?
[09:23] <apw> so we can tell if this is a problem with the backports or generally, or indeed a bug in libreoffice
[09:28] <ricotz> apw, I don't have i386 system to test this, so I am only seeing this on launchpad's i386 builders if the testsuite is made fatal
[09:29] <ricotz> due to this issue libreoffice packaging was patched to ignore failing tests on i386 to have it built
[09:30] <apw> how i wish we had shit-canned 32bit in xenial
[09:30] <klebers> ricotz, what's the libreoffice version that's failing?
[09:31] <apw> ricotz, well presumably one could fire up a 32bit image in kvm and test there
[09:31]  * apw leaves ricotz in klebers' capable hands
[09:31] <ricotz> it is not restricted to libroffice it is a jvm issue
[09:31] <klebers> I can try doinf that
[09:32] <klebers> ricotz, do you have a link to any log or something that could provide enough information to try to reproduce the problem manually on a vm?
[09:33] <icey> apw: I get "Address not found" errors for kernel-team@canonical.com and @ubuntu.com
[09:34] <ricotz> klebers, https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1436980.html , https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303
[09:34] <tjaalton> icey: @lists.ubuntu.com
[09:34] <icey> thanks tjaalton 
[09:35] <apw> icey, @lists.ubuntu.com
[09:36] <apw> trying to not say both bits together :)
[09:36] <icey> apw: wouldn't want somebody getting spam onto the mailing lists ;-)
[09:36] <apw> oh we get plenty anyhow
[09:37] <ricotz> klebers, you should be able to reproduce this with any libreoffice i386 package in the archive
[09:40] <klebers> ricotz, so it's reproducible not only on build but also on simply starting it?
[09:54] <ricotz> klebers, yes, as it is documented in e.g. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772
[12:23] <icey> mhcerri: regarding that patch update email for the yoga 910, given that I'm just trying to supply somebody elses patch (submitted upstream), seems strange to edit their commit to include the bug link? 
[12:24] <mhcerri> hi, icey. no, that's standard practice. just make sure to use add a From: line with the original author (git format-patch --from will do that)
[12:25] <mhcerri> icey, this way the original author will be kept when the stable team applies it
[12:27] <mhcerri> you need to make sure it applies to the target kernel, so you probably need to cherry pick it anyway
[12:27] <icey> mhcerri: I haven't even touched that patch file, I merely applied the 3 line change to verify that it works (I've never patched my kernel before ;-P) 
[12:28] <icey> mhcerri: happy to learn, I appreciate the guidance :)
[12:29] <mhcerri> icey, we usually use the ml list to review patches that are ready to be applied to our kernels
[12:29] <icey> mhcerri: is there a good link to use as my git remote for the artful kernel?
[12:29] <icey> mhcerri: understood, sent it to the mailing list at apw's suggestion :)
[12:31] <mhcerri> icey, git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/artful
[12:32] <mhcerri> icey, most of the kernel repos are listed here: https://code.launchpad.net/~ubuntu-kernel/+git/
[13:31] <sforshee> tseliot: do you expect the nvidia driver updates to be done soon? We're planning to put a 4.12 kernel in artful-proposed sometime this week.
[13:59] <tseliot> sforshee: yes, I'll deal with them this week. I've been busy with a couple of deadlines
[13:59] <tseliot> *was
[14:00] <sforshee> tseliot: thanks!
[14:54] <icey> mhcerri: how should I link to the upstream patch, given that the patch hasn't been merged yet?
[14:57] <mhcerri> icey, if it's not possible to wait until it's accepted upstream, you should mark it as "UBUNTU: SAUCE: ", the link has some info about that
[14:57] <mhcerri> icey, you can add some information why it's important in a cover letter or in the commit message
[14:57] <icey> mhcerri: I'd like it in Artful, and I have no idea how long it'll take to get into upstream; per discussion with apw earlier, it is a quirks patch to enable some sensors on a specific model of laptop ;-P
[15:00] <mhcerri> icey, got it. to target artful prefix the subject with "[artful]". that's stripped when applied
[15:00] <mhcerri> icey, `git format-patch  --subject-prefix='artful][PATCH'` will do that for you if you prefer
[15:00] <icey> mhcerri: yeah, once I have this patch formatted, should I send it to the mailing list?
[15:02] <mhcerri> icey, yes, usually `git send-email` is the simplest way to do that  and `--suppress-cc=all` is useful to not bother unrelated people. do you think you are able to build it and test it?
[15:04] <icey> mhcerri: I'm running it custom at the moment, working on building this patch for you :)
[15:11] <icey> mhcerri: do you mind me sending you the patch email before sending to the list to verify that it looks reasonable?
[15:51] <mhcerri> icey, sure. np
[21:53] <nomego> Hi! What's the easiest way to build the ppa-mainline (4.13-rc3) kernel yourself the Ubuntu-way ?