/srv/irclogs.ubuntu.com/2011/06/24/#ubuntu-kernel.txt

=== _LibertyZero is now known as LibertyZero
* apw moans about mumble ... again09:30
ckingshould be called grumble09:38
ppisatiyep, it's really quiet this morning09:40
ckingwe are so busy09:40
ppisatilp 80147310:04
ppisatinominations10:04
ppisatibug 80147310:04
apwbug 80147310:04
apwbug #80147310:04
ppisatithe bot is on strike today10:04
* apw slaps ubot210:04
apwttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/80147310:05
apwthats not a bug10:05
apwnope LP doesn't know that number10:05
apwpp^10:05
apwppisati, ^^10:05
ppisatiuh?10:07
ppisatiwait10:07
ppisatiah10:07
ppisatistill private10:07
ppisatibug 80147310:07
ppisatinow it's pubbli10:07
ppisatic10:07
ppisati*public10:07
apwbug #801473   10:07
ppisaticrap10:08
ppisatiit doesn't work...10:08
apwppisati, approved10:08
apwppisati, this CVE -1082/-1083 where they share the same sha1 fix10:09
apwppisati, for those just put both CVE numbers in the body and let them both go releeased rather than mark them ignored10:10
apwppisati, i've moved 1083 back to needed to mirror -108210:11
apwppisati, i think we should leave th bottom 5 yellow entries, the new ones to be worked as a CVE across teh whole distro10:14
apwas in not just fixed for arm10:15
* apw is going to look at the bottom on (2534) as 'todays' CVE10:15
ppisatidoh!10:31
ppisatiwaity10:31
ppisatii just did the 253410:31
ppisatiand i created the lp bugs for the other 4 news10:31
ppisati...10:31
ppisatithe 4 new one10:31
apwwell thats annoying ... 10:31
apwif you don't mark the awsome tracker i am going to assume they are not done10:32
ppisatiyou mean the cve tracker?10:32
ppisatii'm doing in batch10:32
apwnope that awsome tracker10:32
apwhttps://spreadsheets.google.com/a/canonical.com/spreadsheet/ccc?hl=en&key=tOvtWlTi17QL1bZm-0dCKEg&hl=en#gid=010:32
ppisatiah ok10:33
ppisatidid you do anything?10:33
apwwhats your bug # for 253410:33
apwso i can dup my bug against it10:33
apwi cannot be assed to close all the tasks i just opened10:33
ppisati80147310:33
ppisatiand then i have10:34
ppisati801480 801482 801483 80148410:34
ppisatifor the other 410:34
ppisatiand btw i need nominations acceptance for them10:34
apwug #80148010:35
apwbug #80148010:35
ubot2Launchpad bug 801480 in linux-ti-omap4 "CVE-2011-1170" [Undecided,New] https://launchpad.net/bugs/80148010:35
apwbug #80148210:35
ubot2Launchpad bug 801482 in linux-ti-omap4 "CVE-2011-1171" [Undecided,New] https://launchpad.net/bugs/80148210:35
apwbug #80148310:35
ubot2Launchpad bug 801483 in linux-ti-omap4 "CVE-2011-1172" [Undecided,New] https://launchpad.net/bugs/80148310:35
apwbug #80148410:35
ubot2Launchpad bug 801484 in linux-ti-omap4 "CVE-2011-1173" [Undecided,New] https://launchpad.net/bugs/80148410:35
apwppisati, all done10:36
apwdo put them in the awsome10:36
ppisatik10:37
* apw stops working on cves ..10:37
apwppisati, so do we have open bugs for all the open cves now ?  sounds like you've been opening them10:46
ppisatiapw: yep, for all the cve that i tackle if there's no open bug, i open it10:47
ppisatiand while here, i should report the other cve i've in my queue...10:48
ppisatii mean, in the awesome tracker...10:48
apwif there is no line for them you could add them yes, and for any you have a bug get that in too10:48
apwwe are likely to stop using the tracker once we have proper automation, but we'll need something to seed the links between the cves and bugs, and it may as well be the awsome tracker10:49
apwppisati, i _thnk_ the only one missing is CVE-2010-295510:52
ubot2apw: The cfg80211_wext_giwessid function in net/wireless/wext-compat.c in the Linux kernel before 2.6.36-rc3-next-20100831 does not properly initialize certain structure members, which allows local users to leverage an off-by-one error in the ioctl_standard_iw_point function in net/wireless/wext-core.c, and obtain potentially sensitive information from kernel heap memory, via vectors involving an SIOCGIWESSID ioctl call that specifies a lar10:52
ppisatiwhich link?10:52
ppisati-> "we'll need something to seed the links between the cves and bugs"?10:52
apwppisati, i am saying that to allow any automation to update the bugs from the tracker and visa-versa will need a list of cves against their bug numbers10:53
ppisatiok10:54
ppisatibut why do we need an external tracker? can't we use launchpad for everything?10:55
apwppisati, lunchpuddle doesn't support some of the information in the tracker10:56
ppisatiextending it? :)10:56
apwright :)  i'd like to fix searching so i can find your cves, and they can't do that, so i have no hope they would add anything security needs10:57
ppisatinothing a whip cannot fix...10:58
apw;)10:58
ppisatiok, i think i'm done with the aws tracker11:00
apwppisati, you are doin 2534 right?  i've changed that to you in the at11:01
ppisatiyep11:01
apwok have fun with all those cves11:01
apwppisati, what is the status of 2011-109011:06
apwppisati, are you done with it?  if so i might do teh remaining ports11:08
ppisatiapw: i always do the arm side11:10
ppisatiapw: so yes, hardy is there for you11:10
apwso are you doing the fsl-imx51 for that one ?11:11
ppisatiyep11:11
ogasawarahrm, looks like some of the data for our work items is incorrect @ http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team-oneiric-alpha-2.html14:17
ogasawaraother-kernel-o-ubuntu-delta-review 1 0 0 0 8 89%14:17
ogasawaraStarted14:17
ogasawaraI know for sure we have more than 1 todo items remaining14:18
apwogasawara, hmmm, i could 2-3 depending who is in the c-k-t14:19
apwogasawara, ok the matrix on the oneiric status page, the wiki one, seems to show at least 3, probabally 514:21
ogasawaraapw: that sounds better14:22
apwogasawara, so the database must be ok, but the reports are not right somehow14:22
apwogasawara, as pitti seems quiet, could you remind me in dublin and we can incestigate14:28
ogasawaraapw: yep, I'll throw it on our agenda so we both don't forget14:29
apwogasawara, ahh good plan14:29
* apw has to admit to feeling lax, i am alread thinking about packing14:31
ogasawaraapw: just go pack and have a beer14:34
apwogasawara, i am thinking of the packing part anyhow14:34
ogasawaraI'm thinking of a coffee to wake up, kai won the battle last night14:35
apwogasawara, thats hard for sure ...14:35
apwogasawara, seems its cause the title are the same of the work items, seems we've regressed and are squashing them in the table part though not in the graph15:02
ogasawaraapw: huh, ok.  so I guess I could just fudge the titles to be different for now15:04
apwogasawara, yeah make them [apw] review apw's patches or something15:04
apwand we can try and fix it at sprint15:04
ogasawaraapw: and I'd assume then the one's marked DONE are also afflicted by the same15:06
apwogasawara, yeah i believe so15:06
apwogasawara, do you recall if we report any stats for cves in the weekly meeting ?15:23
ogasawaraapw: I don't think we do15:23
ogasawaraapw: but I would find that info interesting if we did15:23
ogasawaraapw: just to know if we're falling behind processing them15:23
apwogasawara, i was thinking something along the lines of those at the bottom of here, in a digestable form: http://people.canonical.com/~apw/cve/pkg/ALL-linux.html15:24
apwogasawara, probabally just and overall number, 21 cves open some some release sort of thing15:24
ogasawaraapw: yep, that would be nice15:25
apwi think i can make this page produce all the numbers one might care for ... hmm something to consider15:25
ogasawaraapw: we sure have a lot of 'pending' ones15:26
apwogasawara: yeah though that is triggered by them either being in -proposed only or if kees has not yet run a reconcilliation against the usns15:40
apwogasawara: and i think we are pending quite a bit both ways15:40
apwfor us any sort of green is positive, and will resolve itself without further interaction from anyone but stable15:44
ogasawaraapw: so is our CVE workflow ironed out now, eg security team opening bugs to drive our work etc.15:45
apwogasawara: not yet, the last bits are meant to be finished by next week, we are meeing with -security to iron it all out15:49
ogasawaraapw: cool, didn't know if we needed to add it to the agenda but sounds like you guys are already set to meet15:50
apwogasawara, if you have the agenda on your browser lets add something to remind us15:50
ogasawaraapw: ack, I'll add it since I'm staring at it right now15:50
apw(is the release meeting in 10m?)15:51
ogasawaraapw: yep, I got it covered15:51
apwi don't doubt you are prepared :)15:51
hyperairmanjo: ping15:56
hyperairmanjo: i happened to stumble upon http://permalink.gmane.org/gmane.linux.kernel.input/19005 while attemptnig to find a fix/workaround for my e220s. did you make nay progress on that issue?15:57
hyperairlast post seems to be april15:57
manjohyperair, its a bios issue ... if you load your module with proto=bare you can work around it 16:01
hyperairmanjo: proto=bare detectss only a single device.16:06
hyperairand both the touchpad and trackpad work through it16:06
hyperairas a result, the touchpad doesn't work with synaptics16:06
ogasawaraapw: bah, I had an old release schedule for O, Alpha2 is the week after rally16:07
ogasawaraapw: so I'll plan to upload our final Alpha2 kernel Friday of the rally16:07
hyperairmanjo: also, my bios doesn't seem to have a setting to disable the touchpad =\16:07
apwogasawara: ok, well we should probabally still go for something today as its been a while16:08
ogasawaraapw: yep, still plan to upload after the release meeting16:08
manjohyperair, yeah ... I know ... I did email the guys at lenovo about this ... and have not seen a bios  that fixes that 16:08
ogasawaraapw: will you be able to watch for any fires the week of Alpha2, I'll keep an eye too even though technically being on vacation16:08
hyperairmanjo: did you receive a reply from them?16:09
manjohyperair, I got an email from them saying synaptic is looking at it 16:09
hyperairah i see16:09
hyperairhmm16:09
apwogasawara: yeah of course16:09
apwogasawara: unless we are totally on fire its a noop anyhow for us16:09
hyperairmanjo: a matter of time, eh.16:09
ogasawaraand here I tried so hard to schedule vaca around the milestones16:09
manjohyperair, good that you reminded me ... I need to ping them again on this ... been a while 16:09
hyperairmanjo: np.16:10
hyperairactually if you could CC me as well, that would be great. i'd like to hear when a fix comes out =)16:11
apwppisati: did the usb fixes get committed yet?16:25
ppisatiapw: yep17:11
=== emma is now known as em
apwppisati, cool thanks ... must make sure they are uploaded early next week if they have not already17:24
ppisatiapw: right, i've a couple of pull req pending17:26
apwppisati, sounsd good, thanks17:27
=== kamal1 is now known as kamal
=== kamal is now known as Guest85291
=== Guest85291 is now known as kamalmostafa
lmn123What does this dmesg line mean ?19:19
lmn123[    1.731033] sata_svw 0000:01:0e.1: PCI INT A -> GSI 11 (level, low) -> IRQ 1119:19
=== kamalmostafa is now known as kamal
=== Quintasan_ is now known as Quintasan
=== yofel_ is now known as yofel
apwlmn123, its telling you how PCI interrupta are being connected up and delivered21:08
ckingapw, isn't it beer time?21:14
lmn123apw, http://pastebin.com/4pv4Zivv21:20
lmn123 By observing the time diff in consecutive lines, does it look normal ?21:21
lmn123line 7 and 821:21
lmn123apw, here is the correct link. http://pastebin.com/hzkYZ3nS21:22
smoserapw, are you actually stlil around?21:32
smoserbug 801408 is what i reported about a week ago. i saw it again and tried to collect some more info.21:33
ubot2Launchpad bug 801408 in linux "out of memory, dont know why" [Undecided,Confirmed] https://launchpad.net/bugs/80140821:33

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!