=== _LibertyZero is now known as LibertyZero === ogasawara_ is now known as ogasawara === ogra is now known as Guest4143 === Guest4143 is now known as ogra_ === ogra is now known as Guest69691 === Guest69691 is now known as ogra_ [11:38] apw: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=blob;f=net/unix/garbage.c;h=736e6f94c282d7b271b6cd17a7eb9cf7739fceb9;hb=refs/heads/fsl-imx51 [11:39] apw: http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=9915672d41273f5b77f1b3c29b391ffb7732b84b [11:39] apw: CVE-2010-4160 [11:39] ppisati: Multiple integer overflows in the (1) pppol2tp_sendmsg function in net/l2tp/l2tp_ppp.c, and the (2) l2tp_ip_sendmsg function in net/l2tp/l2tp_ip.c, in the PPPoL2TP and IPoL2TP implementations in the Linux kernel before 2.6.36.2 allow local users to cause a denial of service (heap memory corruption and panic) or possibly gain privileges via a crafted sendto call. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4160) [11:47] apw: this is in our maverick/ti-omap4 tree: d428c4f08e29958d3d9dd3a2ea846ef5fce0366d [11:48] apw: and it's actually the cve fix: 9915672d41273f5b77f1b3c29b391ffb7732b84b [11:48] i remember that bug [11:49] bliss: good memories are hard to fade out :) [11:49] ha [11:49] the fix was putting in upper bounds on maximum iovec sizes in the sendmsg syscall path [11:50] so that's the fix that should be backported, not just the corrections to the l2tp code [11:50] should prevent a bunch of other undiscovered vulns [11:50] let me peek at those commits [11:51] bliss: i mispsated the CVE number, we are referring to 2010-4249 actually [11:51] heh [11:51] that's the unix socket DoS? [11:51] that one looked like a pain to fix [11:51] bliss: unic gc [11:51] unix [11:52] * ppisati today is unable to type anything correctly... [11:53] heh, no worries [11:55] Hi, I have a kernel regression with a CDROM device (worked on lucid, doesn't work on maverick/natty). On the other hand, sandy bridge doesn't work on lucid, so I'm stuck with either the CDROM or the network adapter not working [11:55] How can I try the oneiric kernel to my lucid box? [11:55] I tried the latest from http://kernel.ubuntu.com/~kernel-ppa/mainline but module-init-tools version is incompatible [11:57] Can I install module-init-tools from oneiric to my lucid, or will that break something else? [11:57] Ah, no, dpkg version incompatible there [12:15] lamont: were you able to test this one?: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791512/comments/15 [12:15] Ubuntu bug 791512 in linux-meta "tcp connections hang in forwarding machine" [Undecided,Invalid] === chrisccoulson is now known as chrisccoulson_ === chrisccoulson_ is now known as chrisccoulson [12:52] I tried with the latest oneiric live cd: Linux ubuntu 3.0-2-generic #3-Ubuntu SMP Fri Jun 24 19:09:43 UTC 2011 i686 i686 i386 GNU/Linux [12:52] The regression is still there, i.e. the CDROM drive that is recognized in Lucid, is no longer recognized in Maverick, Natty and Oneiric. [12:52] Where would I file a bug for that? === ogra is now known as ogra_ [12:53] And, I'm not the one having the problem, I'm remote-supporting a fellow teacher, so I'd better gather any needed data now, I don't think he'll be able to do it himself later... [12:53] hi all, what's the reason all packages were pulled from the kernel ppa on launchpad? [12:54] is there a new suggested way for updating to 2.6.39+? (i'm on natty) [13:52] Hey guys. Could Ypu help me? I don't know how to apply Ubuntu-specific patch on vanilla kernel. Downloaded linux-source-2.6.38.deb, installed it. In /usr/src/linux-source-2.6.38 I have folders: debian, debian.master and vanilla kernel archive: linux-source-2.6.38.tar.bz2. How should I proceed? Please help. I know only how to patch kernel with diff's :( [13:53] Could You* [14:49] sbte: those were just testing kernels, preparitory to those being then in the real archive [15:49] if only I had used askubuntu.com sooner. http://askubuntu.com/questions/4653/how-do-i-get-rid-of-u3-system-on-my-usb-drive [16:07] hi, I was trying to grab a package from the kernel team's PPA but looks like the page is currently empty (https://launchpad.net/~kernel-ppa/+archive/ppa), thus apt-get ignoring to update the repository. Any clue on how I can move forward? (I am on Lucid LTS) [16:14] and: those were just testing kernels, preparitory to those being then in the real archive [16:14] and: the lts has official packages that replace those [16:15] apw, ok, but I am actually running on 2.6.32-32, is there a way to download/install 2.6.38 for example? [16:16] should I grab them on http://kernel.ubuntu.com/~kernel-ppa/mainline/ and manually install? [17:10] ogasawara, were you looking for me ? [17:10] manjo: no, cking was [17:10] manjo: he's just left to go find you [17:11] ogasawara, ok thanks [17:59] apw, sorry, xchat crashed. In reply to you: I know, but is there a different suggested way to update to a newer version of the kernel? I need it because 2.6.39+ has builtin wifi drivers for my card that don't cause kernel panics === ogra is now known as Guest32535 === Guest32535 is now known as ogra_ [20:38] Hi, I'm trying to bisect a kernel and while building, apart from the bisect, I change only the changelog with numbers ~bgo1234vish0 , ~bgo1234vish1 and so on.. but when I check using $uname -a after booting into the newly build kernel, it only shows as ~bgo1234vish0 , the first build version number while the package number is the right one. [20:39] is that OK, or am I not building the right version? [20:39] or how do I fix that numbering which displays in $uname -a ? === yofel_ is now known as yofel [22:34] heya, I've been helping Stefan Stasik with a kernel bug on arrandale - lp #758785 [22:34] Launchpad bug 758785 in xserver-xorg-video-intel "[arrandale] Display flickers or blank on login (x86_64)" [Undecided,Invalid] https://launchpad.net/bugs/758785 [22:35] he's in the process of bisecting, and has a patch flagged that he's going to try and test (which I've linked on the bug) [22:36] I've tagged the bug kernel-handoff-graphics, but also pinging here since I think the bug may be close to solution and could probably benefit from a kernel engineer's attention