=== sekrit is now known as CIA
[08:00] <mercutio> i noticed that ubuntu trusty seems to have the xenial lts kernel available already.  is this already considered stable?
[08:00] <mercutio> it seems that options are to have a kernel that's only supported until August, or use xenial kernel?   and there seems to be an unpatched bug in 3.13...
[08:52] <apw> mercutio, 3.13 is the release kernel so has 5 years of support ...
[08:53] <mercutio> but it's not an upstream lts support version so only vulnerabilities are fixed?
[08:54] <mercutio> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423672
[08:54] <ubot5`> Launchpad bug 1423672 in linux (Ubuntu Trusty) "ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y" [High,Confirmed]
[08:54] <mercutio> i was looking at that bug which doesn't seem to be fixed
[08:55] <apw> mercutio, lts-xenial i would not normally suggested until the .1 release of the lts, it is considered an early preview before then
[08:55] <mercutio> so would 4.2 be recommended for something to use for a long time?
[08:56] <mercutio> having file system corruption bug of course is not really desired
[09:33] <apw> kamal, ^
[12:06] <arges> mercutio: looks like there was a patch (7dec560e) identified that fixes that issue, so that seems like a reasonable thing to fix in 3.13 as well
[12:08] <mercutio> arges: yeah, there was a short patch identified
[12:09] <mercutio> but i checked gitweb and it wasn't in
[12:10] <arges> mercutio: this is our kerenl SRU process: https://wiki.ubuntu.com/KernelTeam/KernelUpdates 
[12:13] <arges> mercutio: so I could submit this as an SRU and then when the update comes into 3.13 someone would need to test it and verify it does fix the issue, then eventually it is released
[12:13] <mercutio> arges: what kind of time frame is there for that?
[12:14] <arges> 3-6 weeks
[12:14] <arges> if it is verified quickly and causes no regressions
[12:14] <mercutio> i see
[12:15] <mercutio> yeh i think i waant to change kernels quicker than that personally
[12:21] <arges> well this is probably worth fixing it for other users too, I'll post a test kernel on the bug regardless
[12:34] <mercutio> yeah it's definitely worth fixing
[12:58] <arges> mercutio: ok commentd on the bug with a test kernel
=== henrix_ is now known as henrix
=== henrix_ is now known as henrix
=== shuduo is now known as shuduo-afk
=== alvesadrian is now known as adrian