Syscalls, Kernel vs. User Mode and Linux Kernel Source Code - bin 0x09

It's a shame you have so little views. I think your videos are awesome! It's very hard to get into "hacking" or basically understanding how computers really work in a fun way. I appreciate your effort to make this knowledge easier to acquire. Thank you!

Your videos are very good. I have searched and watched many videos on the topic in matter and your work is what exactly i was looking for. Well explained terms, examples with live hands-on-keyboard, short length, references from books used, no sleepy voicing and many more. Your videos are an example of how video tutorials-lectures should be made. Congrats

It was sure I/Opening :D

9:06 "Imagine if a process try to read some secrets from another process". A few days ago (January 2018) the google project zero team discovered a bug that does exactly this (meltdown and spectre) hahahaha

I thought Linux kernel was complicated. Now I'm sure. Actually it's the simpler it can be, computing is complex and providing a safe reliable bed for applications to run, live and exit is indeed... Magic. Highest rank of Computer Magic.

im learning a lot from your videos, thanks for taking the time to make them, i appreciate it

This is more my speed. A lot of condensed information in a short time here. Definitely going to have to wake up and drink another cup of coffee before watching it again.

This is amazing, never seen a video before that actually links all these concepts together, this gave me a totally new point of view on this as a student, thank you!

This video is very good and you are really good at explaining complex stuff. This of course requires making some simplifications and it's quite easy to make things wrong when you do that. Claiming that the mov instruction inside of __get_user_asm is an example. While this is possible, its not what will usually happen. In most cases the page will be available in the memory (won't be swapped out) and no page fault will be done. As you explained before, resolving virtual addresses is done transparently by MMU, which is reprogrammed each time a process is scheduled.

Your English is quite clear and easy to understand by non-native English users

no matter how many times I come back to this playlist, I always learn something new🙌

nice , but you wrong at 11:57 there will be no page fault ( only happen on special cases like addresses not belong to the process address space or swapped ) kernel will be mapped across all processes ( but protected from access ) so kernel can access process memory just by VA and MMU will convert to PA as usual

0:50 the funny thing about calling them an interface between things, is that the interface itself must then exist in a domain of its own (otherwise it isn't an "interface" but part of one "face" inside another - difference is crucial), of course being again either user or kernel land. In reality syscall implementation always exists in both of course.

you are amazing!. this compliment is not for what i learn from your videos. it is for your way of explanation. because, even some topics i don't understand my temptation doesn't stop me that not see your videos. #LiveOverflow is one of the best channel i am following thank you.

watched 2 times to get the grasp of it. Man it was really profound amount of knowledge.

Great series so far. You are the first person I have found that goes deep enough to make me think, but not to the point of confusion. I appreciate what you are doing, keep up the good work!

I love your videos. It is good to dive into topics like this sometimes. It is a taster that makes me want more.

I did not understand the syscall code part. Not your fault.. I m a noob linux kernal programming It inspires Me to Start learning more about these Thanks

I started learning the assembly and found it really difficult. Hope watching your video will help me more in learning :D

RDMSR(Read MSR) is a kernel level command how it can be execute in user mode,so there is much detail you are missing but its a great video