[07:49] <fairuz> Morning 
[08:37] <diwic> hi! what's the magic git command to figure if a commit is in the master-next branch of ubuntu-natty (and thus will be in the Natty final kernel), or if I have to ask for it explicitly on the kernel-team ML?
[08:38] <smb> diwic, You know you just can look at that branch? git log origin/master-next
[08:39] <smb> (from a natty tree that is)
[08:39] <diwic> smb, right, then I can pipe that to grep. Didn't think of that, thanks.
[08:40] <smb> diwic, there would even be a --grep="bla" for git log
[08:42] <RAOF> I believe there's even a “git contains” somewhere... let me se.
[08:42] <smb> RAOF, You probably mean git describe --contains <sha1>
[08:43] <RAOF> smb: I do indeed.
[08:44] <smb> The downside there is that you need a sha1 on natty maybe still be able to be rebased makes it hard to know that
[08:45] <smb> Actually master-next is never linear
[11:05] <smoser> hey. i just opened bug 752352
[11:05] <smoser> is this expected behavior ?
[11:06] <smoser> it was not listed in the changelog.
[11:41] <tim> hi. is it possible to build the linux-tools package with make-kpkg?
[11:51] <smoser> smb, you know anything about bug 752352 ?
[12:19] <smb>  smoser Could be a security feature... I remember kees was asking about some file permissions recently
[12:19] <smoser> its not listed in changelog.
[12:19] <smoser> and the files are publically available on launchpad or apt repository
[12:20] <smoser> so just plain hiding their content isn't all that useful.
[12:20] <smoser> ie, if i can't read it in /boot i can download the deb myself 
[12:22] <smb> Well, I am the wrong person to argue about that. ;) But it makes it harder for automated attacks I guess.
[12:23] <smb> See "UBUNTU: [Config] packaging: adjust perms on vmlinuz as well"
[12:26] <smb> smoser, Is that a real problem. At least for starting instances one needs to be root anyway...
[12:26] <smoser> not a problem for starting anything
[12:26] <smoser> but caused my builds to break
[12:26] <smoser> they assume that they can read contents of /boot 
[12:26] <smoser> to copy the kernels out
[12:27] <smoser> they can very easily be root to do that, the scripts just be root as little as they have to
[12:27] <smb> smoser, Doh! 
[12:29] <smb> smoser, The reasoning from the patch is that exploits could get the location of kernel addresses from there. I agree that they can have locations prepared per kernel versions...
[12:30] <smoser> so that *is* intended behavior ?
[12:31] <smb> smoser, It was a change that was requested by the security team, yes
[12:31] <smoser> and, by design not listed in the changelog
[12:31] <smoser> :-(
[12:31] <smb> It should be in the changelog
[12:31] <smb> It is at least referenced there in the file
[12:32] <smb> linux (2.6.38-8.40) natty; ...
[12:32] <smb> ...
[12:32] <smb> * [Config] packaging: adjust perms on vmlinuz as well
[12:33] <smb> I am ready to admit that this is not that obvious
[12:33] <smoser> ah. sorry. i looked in the specific binary's config
[12:34] <smoser> oh, and it is there also...  i just looked at the top entry
[12:34] <smoser> sorry for the spam
[12:34] <smb> no worries. There is a lot of text in the changelog at the end of a day
[12:40] <smoser> thank you smb 
[12:59] <arand> It seems that the latest -8 kernel makes update-grub not create the subvol=@ entry (for btrfs), are there any changes which could be related to that?
[13:10] <aakshay> i have made small "hello" type driver.. now  i would like to start with desigining drivers for ubuntu. please suggest me how should i start?
[13:12] <aakshay> sconklin, i have read the book you suggested me and tried the basic examples. now please suggest me to start development with community. :)
[13:13] <fairuz> aakshay: which book? LDD?
[13:13] <aakshay> fairuz, yes..
[13:14] <aakshay> fairuz, it gave me the basic idea only.. how to go further ?... :)
[13:14] <fairuz> aakshay: for me the book is complete :D So what did you managed to do until now
[13:15] <fairuz> external module? 
[13:15] <aakshay> fairuz, i  designed the basic initialization module.  
[13:16] <fairuz> and what did you initialized?
[13:16] <arand> Is there any http acces to the git repos of ubuntu by the way?
[13:16] <aakshay> fairuz,  a simple function... :p
[13:16] <aakshay> which displayed some info like " entering the module" 
[13:17] <aakshay> fairuz, means very basic.. :D
[13:17] <fairuz> aakshay: So have you tried to do some communication between user space and kernel space?
[13:17] <aakshay> fairuz, nah.. not yet :(
[13:17] <fairuz> aakshay: so i think you better try that first
[13:17] <aakshay> should i go for that now?
[13:17] <aakshay> ok :)
[13:17] <fairuz> aakshay: http://www.freesoftwaremagazine.com/articles/drivers_linux?page=0%2C3
[13:17] <fairuz> a good tutorial 
[13:18] <fairuz> aakshay: http://www.freesoftwaremagazine.com/articles/drivers_linux?page=0%2C0 this is the first page
[13:18] <aakshay> okiez.. i will do according to this tutorial
[13:18] <aakshay> :)
[13:18] <aakshay> okiez..
[13:18] <aakshay> but to run these modules, do i need my own build kernel?.. ;p
[13:19] <fairuz> this tutorial is for our of tree modules
[13:19] <fairuz> it means you just need the kernel source to build it
[13:19] <fairuz> no need to recompile your kernel 
[13:19] <fairuz> *out
[13:19] <fairuz> *out of tree
[13:20] <aakshay> fairuz, ok but please tell me something. i am designing all these codes in the kernel directory of my normaly ubuntu i am using
[13:20] <aakshay> i have not built any separate kernel
[13:20] <fairuz> no problem with that
[13:21] <aakshay> ok..
[13:21] <fairuz> you compile a module for a specific kernel
[13:21] <aakshay> fairuz, thankyou so much...
[13:21] <fairuz> if you are compiling using your currrent kernel, then it will run only on the current kernel
[13:21] <aakshay> okiez... but what specific kernel means here?  :-o
[13:21] <fairuz> the kernel that you are using :D
[13:21] <fairuz> type uname -r in your terminal to see which kernel you are using
[13:22] <aakshay> fairuz, okiez... :p
[13:22] <aakshay> fairuz, thanks a lot.. can you please tell me how long will it take to complete with this tutorial? :p
[13:22] <fairuz> aakshay: 30 minutes ?
[13:23] <fairuz> or less
[13:23] <aakshay> ohhhh!!!! .... :D
[13:23] <aakshay> fairuz, so let me try this to complete this in 30 minutes
[13:23] <aakshay> :P
[13:23] <fairuz> aakshay: ok, but you need more time to understand... dont just copy paste the code
[13:24] <aakshay> fairuz, yes..  thanks a lot... :)
[13:24] <fairuz> do page 1 to page 7 of the tutorial
[13:24] <fairuz> aakshay: np
[13:24] <aakshay> fairuz, okiez.. let me start noe itself
[13:24] <aakshay> :P
[13:24] <aakshay> *now
[13:49] <arand> It seems that the latest -8 kernel makes update-grub not create the subvol=@ entry (for btrfs), are there any changes which could be related to that? Also, is there any git http access so one could clone the repos and have a look? (I'm badly firewalled).
[13:49] <tgardner> arand, http://kernel.ubuntu.com/git
[13:54] <arand> Hmm, I don't see any http links there, and using git clone http://kernel.ubuntu.com/ubuntu/ubuntu-natty.git fails...
[14:01] <fairuz> arand: git clone git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git
[14:02] <arand> fairuz: I am firewalled and can't use the git:// protocol (unless I go through tor, at 60K/s ...).
[14:13] <ogasawara> diwic: bug 732445, looks like you mention the patch has landed upstream in the takashi's sound-2.6 tree, did you want it applied as pre-stable to natty?
[14:14] <diwic> ogasawara, let me see
[14:15] <ogasawara> diwic: if so, care to just send a quick email to the list
[14:15] <diwic> ogasawara, ok, I want it in
[14:18] <diwic> ogasawara, I think it's already in
[14:19] <diwic> ogasawara, it's just that since Takashi chose a different solution he took away my buglink in the process
[14:19] <ogasawara> diwic: ok cool
[14:20] <diwic> ogasawara, if git log origin/master-next --grep 584c0c4c359 says it's in, it's in, right?
[14:20] <ogasawara> diwic: yep, it's in
[14:21] <ogasawara> git describe --contains 24449f05b663f1984ee6ecdba5a0d2ff2a1e0462
[14:21] <ogasawara> Ubuntu-2.6.38-8.40~661
[14:27]  * ogasawara back in 20
[15:00] <aakshay__> fairuz, am back. :)
[15:00] <aakshay__> understood the coe
[15:00] <aakshay__> *code
[15:00] <fairuz> aakshay__: make it worked then?
[15:00] <aakshay__> but while running , i am getting the error :(
[15:00] <aakshay__> "error: expected declaration specifiers or ‘...’ before ‘sizt_t’
[15:00] <aakshay__> "
[15:00] <aakshay__> fairuz, :(
[15:01] <fairuz> aakshay__: try to debug it :D it should give you the line number 
[15:01] <aakshay__> fairuz, its taking ssize_t  as  'sizt_t' 
[15:01] <aakshay__> yes its line 17 and 18
[15:01] <fairuz> aakshay__: check your code. You do copy paste from the site or write it on your own?
[15:02] <aakshay__> i took the same code but wrote myself.. 
[15:02] <aakshay__> fairuz, so that i will learn :p
[15:03] <fairuz> whats on line 16 to 18?
[15:03] <aakshay__> please wait.. let me copy the code on pastebin.com
[15:03] <aakshay__> :p
[15:04] <aakshay__> fairuz, its "http://paste.ubuntu.com/590256/"
[15:05] <fairuz> aakshay__: As i said before, take a good look at the code and you will find it
[15:05] <fairuz> you miss spell something on line 17 and 18
[15:05] <aakshay__> oops!! .. let me check.. ;p
[15:06] <aakshay__> hehe.. :D.. such a silly mistake.. n took lot of time to get corrected.. :p.. thanks.. 
[15:06] <aakshay__> let me compile again.. :)
[15:07] <aakshay__> fairuz, yipii.. done!!
[15:07] <aakshay__> :)
[15:07] <fairuz> aakshay__: When it says error at line 17, don't look at line 40..  =)
[15:09] <aakshay__> fairuz, :p... i looked at line 17 only.. :D... i was only lookin at ssize_t , not on required variable.. :D
[15:15] <aakshay__> fairuz, its done.. :).. and i understood it well.. please tell me what i can do further?
[15:15] <fairuz> aakshay__: you tried to insmod and rmmod your module? it worked?
[15:15] <aakshay__> yes
[15:15] <aakshay__> i removed the modules
[15:15] <aakshay__> an checked them using the lsmod command
[15:16] <aakshay__> :)
[15:16] <aakshay__> *and
[15:16] <fairuz> aakshay__: you tried to communicate with your module from user space?
[15:17] <aakshay__> fairuz, dont know
[15:17] <aakshay__> :p
[15:18] <fairuz> aakshay__: so you dont completed the tutorial -.-"
[15:18] <aakshay__> i entered the data. it was from the user space then its copied to kernel space to be accessed from /dev/memory
[15:19] <aakshay__> :p
[15:19] <aakshay__> fairuz,  is this was not the concept?.. :)
[15:21] <aakshay__> fairuz, oh yes.. you are right.. the data in the tutorial is sent directly using the "echo" command 
[15:22] <aakshay__> there is no use of functions "copy_from_user" and so
[15:22] <aakshay__> :P
[15:25] <aakshay__> fairuz, i have not done the "parallel port" part...
[15:25] <aakshay__> fairuz, how can we make use of the functions "copy_from_user" and others ?
[15:35] <tgardner> bryceh_, no joy on bug #686388
[15:43] <aakshay__> fairuz, thanks for help.. :).. i have to leave. good bye.. . :)
[15:45] <tgardner> smb, do you remember how to skip failing mounts at boot up? mountall is hanging 'cause /dev/md0p1 hasn't been enabled when /etc/fstab is read.
[15:46] <smb> tgardner, typing s
[15:46] <smb> though it might work only with splash
[15:46] <tgardner> smb, k, I'll go try that.
[15:54] <tgardner> smb, huh, it even tells you what to do, but you have to be able to see the console.
[15:55] <smb> tgardner, Sort of makes sense as you are usually in front of it to type the letter
[15:57] <smb> tgardner, This is where I start to like boards with integrated ipmi module. The only thing I have not yet got running is to get the java based graphical console over a tunnel when I am not in my home network. :)
[15:58] <tgardner> smb, I suppose this emerald has that, but I'm just too lazy to get it working. I'll only have it for a limited time.
[16:01] <smb> tgardner, Too true. It was relative simple here as it got its own lan port. The only annoying part is that it only runs with sun-java installed (he graphical console)
[16:19] <JFo> <-lunch and a few errands
[16:19] <JFo> bbiab
[16:46] <bjf> ogasawara, these are probably already on your radar: http://people.canonical.com/~kernel/reports/regressions-proposed-report.html
[16:48] <ogasawara> bjf: thanks, I'll browse through em to just make sure there's no kittens dieing
[16:48] <tgardner> ogasawara, no pink kittens this time around? how about green?
[16:49] <tgardner> or is that dyeing ?
[16:49] <tgardner> I can never remember
[16:49] <ogasawara> heh, I can never remember either
[16:59] <tgardner> ogasawara, ooh! I fixed bug #747364. do I get brownie points ? I used the "Won't Fix" club.
[17:00] <ogasawara> tgardner: heh, I'll buy ya a beer in budapest
[17:00] <tgardner> ogasawara, big spender. it'll only cost you $1.80
[17:01] <ogasawara> tgardner: diapers are expensive these days, it's all I can afford :)
[17:01] <tgardner> ogasawara, go cloth
[17:02]  * smb tries not to think too much about the term brownie points now
[17:02]  * tgardner thinks smb is a sick puppie
[17:02] <bjf> ogasawara, i don't know if "fixing a bug" by marking it "won't fix" constitutes a beer, but maybe a 1.80 beer
[17:46] <tgardner> ogasawara, how are your oneiric armel build issues coming?
[17:46] <ogasawara> tgardner: should be fixed, final build is just finishing up
[17:46] <ogasawara> tgardner: I pushed the bits to the repo
[17:46] <tgardner> ogasawara, cool
[17:46] <ogasawara> tgardner: am about to rebase to 2.6.39-rc2
[17:47] <tgardner> ogasawara, which will introduce a whole new raft of issues :)
[17:48] <tgardner> ogasawara, don't forget to pick up master-next commits
[17:48] <ogasawara> tgardner: ack
[18:22] <kristian-aalborg> jjohansen: ping
[18:25] <jjohansen> kristian-aalborg: pong
[18:26] <kristian-aalborg> I've been thinking.... the install I tested my custum kernels on is kind of a mess since I have experimented a lot
[18:27] <jjohansen> yeah that happens
[18:28] <kristian-aalborg> fun times indeed... but it may be a factor in my kernels messing up
[18:29] <kristian-aalborg> or anyway, that thought crossed my mind
[18:29] <jjohansen> yes that is possible
[18:29] <JFo> oh hey jjohansen, you pinged me the other night but I just missed you when I responded. Do you still need me?
[18:30] <jjohansen> generally we try to build inside a chroot to keep the environment consistent
[18:30] <jjohansen> JFo: hrmm, I can't remember why I pinged you, so you are in the clear :)
[18:30] <JFo> oh good :-)
[18:31] <jjohansen> JFo: hrmm maybe it was for a bug nomination
[18:31] <JFo> could be
[18:31] <JFo> if you remember it I am happy to fix it
[18:31] <JFo> or rather approve it
[18:32] <JFo> jjohansen, was it to add a linux(Ubuntu) task to this one? https://bugs.launchpad.net/linux/+bug/744419
[18:33] <jjohansen> JFo: actually it was Bug #748656
[18:34]  * JFo looks
[18:34] <JFo> jjohansen, done
[18:35] <jjohansen> JFo: so Bug #744419 is not kernel related, we traced it down to eucalyptus
[18:35] <jjohansen> or at least that is the current working theory
[18:36] <JFo> ah hah
[18:36] <jjohansen> kvm runs fine, and this is failing when we put in the maverick kernel
[18:36] <JFo> well, I added a kernel task just in case
[18:36] <JFo> if it isn't needed it is an easy thing to close
[18:36] <JFo> just don't want it to disappear
[18:36] <jjohansen> so for the moment lets mark the linux task invalid, and we can change it back if needed
[18:36] <JFo> ok
[18:37] <jjohansen> JFo: arg no wait
[18:37]  * jjohansen was looking at the wrong bug
[18:37] <JFo> heh
[18:37] <jjohansen> JFo: that one is linux, its the rtl8192ce driver, traced that one down on the weekend
[18:38] <JFo> ah, I just read your comment
[18:38] <jjohansen> it bugs 746751, that isn't the kernel
[18:38] <jjohansen> we were chasing that on friday and the start of this week
[18:39]  * jjohansen is getting confused by having too many bug tabs open in his browser
[18:39] <JFo> I know the feeling :-(
[18:40] <jjohansen> ogasawara: just a heads up on this one too, bugs 746751 appears not to be kernel related at this time serge is chasing the eucalyptus path
[18:43] <ogasawara> jjohansen: cool, thanks
[18:45] <jjohansen> ogasawara: did smb update you on bug 634487
[18:46] <ogasawara> jjohansen: he mentioned it the other day and I've been following his comments to the bug
[18:46] <jjohansen> ogasawara: okay, great
[18:53] <bryceh_> tgardner, yeah, although upstream had alluded to known issues with macbooks.  I wish Intel were a large enough company to employ more than one engineer in their QA department.
[18:57] <tgardner> bryceh_, thats the only feedback so far. is the macbook a regression?
[18:59] <bryceh_> tgardner, upstreams exact words were "Those two patches have been reported by one user to have fixed the issue for
[18:59] <bryceh_> him, but I need a few more testers since they seem to foul up a MacBook (but
[18:59] <bryceh_> then there are more than one issue at play with MacBooks...)"
[19:00] <bryceh_> so, I would interpret it to mean that yes it is a regression on macbooks
[19:00] <tgardner> bryceh_, gah, what a mess.
[19:02] <bryceh_> maybe if Intel can make some profits they can buy that guy a macbook to test
[19:03] <bryceh_> tgardner, anyway I'm thinking maybe we wait until there's something actually posted to drm-next.  These one off patches seem sketchy too often.
[19:03] <tgardner> bryceh_, ack
[19:04] <kees> smoser: yeah, while the /boot perms obviously don't stop someone from just going and getting the deb themself, it does stop some "simple" attacks that will be dumbfounded by the lack of kernel symbols.
[19:05] <kees> smoser: it's crude and effective for a certain set of attacks, and does nothing to stop others. I felt it was worth it; sorry about the breakage it caused you!
[19:08] <smoser> i really don't think it woudl stop an attack
[19:09]  * tgardner --> lunch
[19:09] <smoser> i really can't imagine someone saying "oh bother, i can't read the kernel symbols for this kernel, i guess i wont' insert a root exploit today"
[19:09] <smoser> "i'd have to do a 'wget' in order to do it, and thats really just too much work"
[19:18] <kristian-aalborg> I'm going to install a backup kernel, I need linux-headers-xxx, linux-image-xxx... and anything more?
[20:05]  * jjohansen -> lunch
[21:56]  * ogasawara back on later
[23:27] <kees> JFo: got a kernel regression for you... 731878