=== gerald is now known as Guest27357
=== psivaa_ is now known as psivaa
=== mwhudson_ is now known as mwhudson
=== yofel_ is now known as yofel
[13:00] <sforshee> apw: did you see the chatter from friday about overlayfs and lxc?
[13:01] <apw> sforshee, hmmm
[13:02] <sforshee> apw: tl;dr is that in wily, overlayfs fstype is mountable in a user namespace but the overlay fstype is not
[13:02] <apw> oh heh, that i could believe, and it would be broken
[13:02] <apw> sforshee, is there a bug for that ?
[13:02] <sforshee> apw: not sure. hallyn?
[13:03] <apw> whever that was discussed it was not here
[13:04] <sforshee> apw: lxc is trying to mount it as overlay if that shows up in /proc/filesystems, so it fails and that's a regression
[13:05] <apw> yep, i am sure we failed to apply the overlayfs fix to allow user mounts to overlay,
[13:05] <sforshee> it's probably a one-line fix, but I wanted to check with you that it's an oversight and not intentional
[13:05] <apw> indeed, and its an oversite
[13:58] <hallyn> sforshee: apw: no i didn't open a new bug.  there are adt failures due to it, wasn't sure if that auto-opens a bug
[13:58] <apw> hallyn, no i don't think it makes ssh-keygen -f "/home/apw/.ssh/ldap_known_hosts" -R togetic.buildd
[13:59] <apw> h yeah thanks
[13:59] <apw> hallyn, no i don't think it makes a bug directly, i assume it is lxc which is failing ?
[13:59] <apw> its self tests
[14:02] <sforshee> apw: yes, lxc tests are failing
[14:02] <sforshee> I've got a patch, just tested it and it's working
[14:02] <sforshee> so I can make a bug and send it
[14:02] <apw> sforshee, ack and ack
[14:03] <hallyn> thanks guys :)
[15:33] <infinity> apw: Has Laney (or anyone) whined at you about the udisks2 autopkgtests OOPSing your kernel on i386?
[15:33] <infinity> apw: http://paste.ubuntu.com/11947918/
[15:34] <apw> not that i have heard about
[15:34] <Laney> нет
[15:35] <apw> infinity, the interesting things there is the first erorr is a disk error
[15:38] <infinity> apw: It's a VM, so neat trick.
[15:38] <apw> yeah, that
[15:38] <apw> a bug would be nice, with the how to run those tests manually
[15:38] <infinity> Laney: ^
[15:39] <Laney> Да
[15:40] <infinity> Laney: Are you trying to tell us that you're being held captive by someone who doesn't have proper keymaps?
[15:40] <infinity> Laney: Is Timmy stuck in the well?  What is it, boy?
[15:41] <Laney> XNOX GOT ME
[15:52] <xnox> infinity: i demand porterbox and early alpha2 release, and Laney will be free.
[15:52] <infinity> xnox: Meh.  You can keep him.
[15:52] <xnox> infinity: he is safe, inside a wall climbing facility.
[15:54] <Laney> Just seal the roof
[15:54] <Laney> apw: bug #1478623
[15:54] <ubot5> bug 1478623 in linux (Ubuntu) "Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test" [Undecided,New] https://launchpad.net/bugs/1478623
[16:51] <wyvern> Hi folks, I'm on 15.04 and I need to use a newer kernel (ideally 4.0 or 4.1) to avoid a usb bug (http://www.spinics.net/lists/linux-usb/msg123652.html). How should I go about doing that?
[16:52] <apw> wyvern, there are no official newer kernels published for that release, you might use the wily kernel which is at 4.0
[16:53] <apw> or is it 4.1, 
[16:53] <rtg> 4.1
[16:53] <wyvern> I don't use ubuntu much; how crazy is it the kernel from a different release?
[16:54] <wyvern> And, assuming it's not too bad of an idea, how would I go about doing so?
[16:54] <wyvern> s/is it the/is it to use the/
[16:54] <apw> we tend to do it pretty often, but you don't get automatic updates that way, so its pretty manual
[16:55] <wyvern> Well right now my usb devices aren't working too well so manual is better than broken :)
[16:56] <apw> you can obtain the debs from the +source/linux page
[16:56] <apw> https://launchpad.net/ubuntu/+source/linux
[16:57] <apw> if you don't have dkms packages, then just the linux-image* and linux-image-extras* package should be sufficient
[16:58] <apw> wyvern, once you find out if 4.1 helps, then it would be good to file a bug (ubuntu-bug linux) saying where its broke and where it works, as that is the starting point for finding out what fixes it
[17:00] <wyvern> OK I'll see what I can do.
[17:50] <unixabg> apw: Greetings, just checking in on the overlayfs things with casper. Any progress?
[17:51] <apw> unixabg, sorry no, been working on some critical cves, which have consumed pretty much all my time, those went out today, so tommorrow might be better
=== adrian is now known as alvesadrian
[21:38] <unixabg> apw: Sounds good and thanks for your willingness to examine the overlayfs things.