[09:30]  * apw moans about mumble ... again
[09:38] <cking> should be called grumble
[09:40] <ppisati> yep, it's really quiet this morning
[09:40] <cking> we are so busy
[10:04] <ppisati> lp 801473
[10:04] <ppisati> nominations
[10:04] <ppisati> bug 801473
[10:04] <apw> bug 801473
[10:04] <apw> bug #801473
[10:04] <ppisati> the bot is on strike today
[10:04]  * apw slaps ubot2
[10:05] <apw> ttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/801473
[10:05] <apw> thats not a bug
[10:05] <apw> nope LP doesn't know that number
[10:05] <apw> pp^
[10:05] <apw> ppisati, ^^
[10:07] <ppisati> uh?
[10:07] <ppisati> wait
[10:07] <ppisati> ah
[10:07] <ppisati> still private
[10:07] <ppisati> bug 801473
[10:07] <ppisati> now it's pubbli
[10:07] <ppisati> c
[10:07] <ppisati> *public
[10:07] <apw> bug #801473   
[10:08] <ppisati> crap
[10:08] <ppisati> it doesn't work...
[10:08] <apw> ppisati, approved
[10:09] <apw> ppisati, this CVE -1082/-1083 where they share the same sha1 fix
[10:10] <apw> ppisati, for those just put both CVE numbers in the body and let them both go releeased rather than mark them ignored
[10:11] <apw> ppisati, i've moved 1083 back to needed to mirror -1082
[10:14] <apw> ppisati, i think we should leave th bottom 5 yellow entries, the new ones to be worked as a CVE across teh whole distro
[10:15] <apw> as in not just fixed for arm
[10:15]  * apw is going to look at the bottom on (2534) as 'todays' CVE
[10:31] <ppisati> doh!
[10:31] <ppisati> waity
[10:31] <ppisati> i just did the 2534
[10:31] <ppisati> and i created the lp bugs for the other 4 news
[10:31] <ppisati> ...
[10:31] <ppisati> the 4 new one
[10:31] <apw> well thats annoying ... 
[10:32] <apw> if you don't mark the awsome tracker i am going to assume they are not done
[10:32] <ppisati> you mean the cve tracker?
[10:32] <ppisati> i'm doing in batch
[10:32] <apw> nope that awsome tracker
[10:32] <apw> https://spreadsheets.google.com/a/canonical.com/spreadsheet/ccc?hl=en&key=tOvtWlTi17QL1bZm-0dCKEg&hl=en#gid=0
[10:33] <ppisati> ah ok
[10:33] <ppisati> did you do anything?
[10:33] <apw> whats your bug # for 2534
[10:33] <apw> so i can dup my bug against it
[10:33] <apw> i cannot be assed to close all the tasks i just opened
[10:33] <ppisati> 801473
[10:34] <ppisati> and then i have
[10:34] <ppisati> 801480 801482 801483 801484
[10:34] <ppisati> for the other 4
[10:34] <ppisati> and btw i need nominations acceptance for them
[10:35] <apw> ug #801480
[10:35] <apw> bug #801480
[10:35] <ubot2> Launchpad bug 801480 in linux-ti-omap4 "CVE-2011-1170" [Undecided,New] https://launchpad.net/bugs/801480
[10:35] <apw> bug #801482
[10:35] <ubot2> Launchpad bug 801482 in linux-ti-omap4 "CVE-2011-1171" [Undecided,New] https://launchpad.net/bugs/801482
[10:35] <apw> bug #801483
[10:35] <ubot2> Launchpad bug 801483 in linux-ti-omap4 "CVE-2011-1172" [Undecided,New] https://launchpad.net/bugs/801483
[10:35] <apw> bug #801484
[10:35] <ubot2> Launchpad bug 801484 in linux-ti-omap4 "CVE-2011-1173" [Undecided,New] https://launchpad.net/bugs/801484
[10:36] <apw> ppisati, all done
[10:36] <apw> do put them in the awsome
[10:37] <ppisati> k
[10:37]  * apw stops working on cves ..
[10:46] <apw> ppisati, so do we have open bugs for all the open cves now ?  sounds like you've been opening them
[10:47] <ppisati> apw: yep, for all the cve that i tackle if there's no open bug, i open it
[10:48] <ppisati> and while here, i should report the other cve i've in my queue...
[10:48] <ppisati> i mean, in the awesome tracker...
[10:48] <apw> if there is no line for them you could add them yes, and for any you have a bug get that in too
[10:49] <apw> we 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 tracker
[10:52] <apw> ppisati, i _thnk_ the only one missing is CVE-2010-2955
[10:52] <ubot2> apw: 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 lar
[10:52] <ppisati> which link?
[10:52] <ppisati> -> "we'll need something to seed the links between the cves and bugs"?
[10:53] <apw> ppisati, 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 numbers
[10:54] <ppisati> ok
[10:55] <ppisati> but why do we need an external tracker? can't we use launchpad for everything?
[10:56] <apw> ppisati, lunchpuddle doesn't support some of the information in the tracker
[10:56] <ppisati> extending it? :)
[10:57] <apw> right :)  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 needs
[10:58] <ppisati> nothing a whip cannot fix...
[10:58] <apw> ;)
[11:00] <ppisati> ok, i think i'm done with the aws tracker
[11:01] <apw> ppisati, you are doin 2534 right?  i've changed that to you in the at
[11:01] <ppisati> yep
[11:01] <apw> ok have fun with all those cves
[11:06] <apw> ppisati, what is the status of 2011-1090
[11:08] <apw> ppisati, are you done with it?  if so i might do teh remaining ports
[11:10] <ppisati> apw: i always do the arm side
[11:10] <ppisati> apw: so yes, hardy is there for you
[11:11] <apw> so are you doing the fsl-imx51 for that one ?
[11:11] <ppisati> yep
[14:17] <ogasawara> hrm, 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.html
[14:17] <ogasawara> other-kernel-o-ubuntu-delta-review 	1 	0 	0 	0 	8 	89%
[14:17] <ogasawara> Started
[14:18] <ogasawara> I know for sure we have more than 1 todo items remaining
[14:19] <apw> ogasawara, hmmm, i could 2-3 depending who is in the c-k-t
[14:21] <apw> ogasawara, ok the matrix on the oneiric status page, the wiki one, seems to show at least 3, probabally 5
[14:22] <ogasawara> apw: that sounds better
[14:22] <apw> ogasawara, so the database must be ok, but the reports are not right somehow
[14:28] <apw> ogasawara, as pitti seems quiet, could you remind me in dublin and we can incestigate
[14:29] <ogasawara> apw: yep, I'll throw it on our agenda so we both don't forget
[14:29] <apw> ogasawara, ahh good plan
[14:31]  * apw has to admit to feeling lax, i am alread thinking about packing
[14:34] <ogasawara> apw: just go pack and have a beer
[14:34] <apw> ogasawara, i am thinking of the packing part anyhow
[14:35] <ogasawara> I'm thinking of a coffee to wake up, kai won the battle last night
[14:35] <apw> ogasawara, thats hard for sure ...
[15:02] <apw> ogasawara, 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 graph
[15:04] <ogasawara> apw: huh, ok.  so I guess I could just fudge the titles to be different for now
[15:04] <apw> ogasawara, yeah make them [apw] review apw's patches or something
[15:04] <apw> and we can try and fix it at sprint
[15:06] <ogasawara> apw: and I'd assume then the one's marked DONE are also afflicted by the same
[15:06] <apw> ogasawara, yeah i believe so
[15:23] <apw> ogasawara, do you recall if we report any stats for cves in the weekly meeting ?
[15:23] <ogasawara> apw: I don't think we do
[15:23] <ogasawara> apw: but I would find that info interesting if we did
[15:23] <ogasawara> apw: just to know if we're falling behind processing them
[15:24] <apw> ogasawara, 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.html
[15:24] <apw> ogasawara, probabally just and overall number, 21 cves open some some release sort of thing
[15:25] <ogasawara> apw: yep, that would be nice
[15:25] <apw> i think i can make this page produce all the numbers one might care for ... hmm something to consider
[15:26] <ogasawara> apw: we sure have a lot of 'pending' ones
[15:40] <apw> ogasawara: yeah though that is triggered by them either being in -proposed only or if kees has not yet run a reconcilliation against the usns
[15:40] <apw> ogasawara: and i think we are pending quite a bit both ways
[15:44] <apw> for us any sort of green is positive, and will resolve itself without further interaction from anyone but stable
[15:45] <ogasawara> apw: so is our CVE workflow ironed out now, eg security team opening bugs to drive our work etc.
[15:49] <apw> ogasawara: not yet, the last bits are meant to be finished by next week, we are meeing with -security to iron it all out
[15:50] <ogasawara> apw: cool, didn't know if we needed to add it to the agenda but sounds like you guys are already set to meet
[15:50] <apw> ogasawara, if you have the agenda on your browser lets add something to remind us
[15:50] <ogasawara> apw: ack, I'll add it since I'm staring at it right now
[15:51] <apw> (is the release meeting in 10m?)
[15:51] <ogasawara> apw: yep, I got it covered
[15:51] <apw> i don't doubt you are prepared :)
[15:56] <hyperair> manjo: ping
[15:57] <hyperair> manjo: 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] <hyperair> last post seems to be april
[16:01] <manjo> hyperair, its a bios issue ... if you load your module with proto=bare you can work around it 
[16:06] <hyperair> manjo: proto=bare detectss only a single device.
[16:06] <hyperair> and both the touchpad and trackpad work through it
[16:06] <hyperair> as a result, the touchpad doesn't work with synaptics
[16:07] <ogasawara> apw: bah, I had an old release schedule for O, Alpha2 is the week after rally
[16:07] <ogasawara> apw: so I'll plan to upload our final Alpha2 kernel Friday of the rally
[16:07] <hyperair> manjo: also, my bios doesn't seem to have a setting to disable the touchpad =\
[16:08] <apw> ogasawara: ok, well we should probabally still go for something today as its been a while
[16:08] <ogasawara> apw: yep, still plan to upload after the release meeting
[16:08] <manjo> hyperair, yeah ... I know ... I did email the guys at lenovo about this ... and have not seen a bios  that fixes that 
[16:08] <ogasawara> apw: will you be able to watch for any fires the week of Alpha2, I'll keep an eye too even though technically being on vacation
[16:09] <hyperair> manjo: did you receive a reply from them?
[16:09] <manjo> hyperair, I got an email from them saying synaptic is looking at it 
[16:09] <hyperair> ah i see
[16:09] <hyperair> hmm
[16:09] <apw> ogasawara: yeah of course
[16:09] <apw> ogasawara: unless we are totally on fire its a noop anyhow for us
[16:09] <hyperair> manjo: a matter of time, eh.
[16:09] <ogasawara> and here I tried so hard to schedule vaca around the milestones
[16:09] <manjo> hyperair, good that you reminded me ... I need to ping them again on this ... been a while 
[16:10] <hyperair> manjo: np.
[16:11] <hyperair> actually if you could CC me as well, that would be great. i'd like to hear when a fix comes out =)
[16:25] <apw> ppisati: did the usb fixes get committed yet?
[17:11] <ppisati> apw: yep
[17:24] <apw> ppisati, cool thanks ... must make sure they are uploaded early next week if they have not already
[17:26] <ppisati> apw: right, i've a couple of pull req pending
[17:27] <apw> ppisati, sounsd good, thanks
[19:19] <lmn123> What does this dmesg line mean ?
[19:19] <lmn123> [    1.731033] sata_svw 0000:01:0e.1: PCI INT A -> GSI 11 (level, low) -> IRQ 11
[21:08] <apw> lmn123, its telling you how PCI interrupta are being connected up and delivered
[21:14] <cking> apw, isn't it beer time?
[21:20] <lmn123> apw, http://pastebin.com/4pv4Zivv
[21:21] <lmn123>  By observing the time diff in consecutive lines, does it look normal ?
[21:21] <lmn123> line 7 and 8
[21:22] <lmn123> apw, here is the correct link. http://pastebin.com/hzkYZ3nS
[21:32] <smoser> apw, are you actually stlil around?
[21:33] <smoser> bug 801408 is what i reported about a week ago. i saw it again and tried to collect some more info.
[21:33] <ubot2> Launchpad bug 801408 in linux "out of memory, dont know why" [Undecided,Confirmed] https://launchpad.net/bugs/801408