Doesn't allowing a user mode program to access kernel space memory and execute the IN and OUT instructions...












2















When the CPU is in user mode, the CPU can't execute privileged instructions and can't access kernel space memory.



And when the CPU is in kernel mode, the CPU can execute all instructions and can access all memory.



Now in Linux, a user mode program can access all memory (using /dev/mem) and can execute the two privileged instructions IN and OUT (using iopl() I think).



So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.



Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?










share|improve this question









New contributor




user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    2















    When the CPU is in user mode, the CPU can't execute privileged instructions and can't access kernel space memory.



    And when the CPU is in kernel mode, the CPU can execute all instructions and can access all memory.



    Now in Linux, a user mode program can access all memory (using /dev/mem) and can execute the two privileged instructions IN and OUT (using iopl() I think).



    So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.



    Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?










    share|improve this question









    New contributor




    user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      2












      2








      2


      1






      When the CPU is in user mode, the CPU can't execute privileged instructions and can't access kernel space memory.



      And when the CPU is in kernel mode, the CPU can execute all instructions and can access all memory.



      Now in Linux, a user mode program can access all memory (using /dev/mem) and can execute the two privileged instructions IN and OUT (using iopl() I think).



      So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.



      Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?










      share|improve this question









      New contributor




      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      When the CPU is in user mode, the CPU can't execute privileged instructions and can't access kernel space memory.



      And when the CPU is in kernel mode, the CPU can execute all instructions and can access all memory.



      Now in Linux, a user mode program can access all memory (using /dev/mem) and can execute the two privileged instructions IN and OUT (using iopl() I think).



      So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.



      Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?







      linux






      share|improve this question









      New contributor




      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 5 hours ago









      ilkkachu

      60.7k1098172




      60.7k1098172






      New contributor




      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 5 hours ago









      user341099user341099

      111




      111




      New contributor




      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      user341099 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          1 Answer
          1






          active

          oldest

          votes


















          7















          So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.




          Well, not all use mode programs can, only those with the appropriate privileges. And that's determined by the kernel.



          /dev/mem is protected by the usual filesystem access permissions, and the CAP_SYS_RAWIO capability. iopl() and ioperm() are also restricted through the same capability.



          /dev/mem can also be compiled out of the kernel altogether (CONFIG_DEVMEM).




          Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?




          Well, maybe. It depends on what you want privileged user-space processes to be able to do. User-space processes can also trash the whole hard drive if they have access to /dev/sda (or equivalent), even though that defeats the purpose of having a filesystem driver to handle storage access.



          (Then there's also the fact that iopl() works by utilizing the CPU privilege modes on i386, so it can't well be said to defeat their purpose.)






          share|improve this answer

























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });






            user341099 is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505527%2fdoesnt-allowing-a-user-mode-program-to-access-kernel-space-memory-and-execute-t%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            7















            So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.




            Well, not all use mode programs can, only those with the appropriate privileges. And that's determined by the kernel.



            /dev/mem is protected by the usual filesystem access permissions, and the CAP_SYS_RAWIO capability. iopl() and ioperm() are also restricted through the same capability.



            /dev/mem can also be compiled out of the kernel altogether (CONFIG_DEVMEM).




            Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?




            Well, maybe. It depends on what you want privileged user-space processes to be able to do. User-space processes can also trash the whole hard drive if they have access to /dev/sda (or equivalent), even though that defeats the purpose of having a filesystem driver to handle storage access.



            (Then there's also the fact that iopl() works by utilizing the CPU privilege modes on i386, so it can't well be said to defeat their purpose.)






            share|improve this answer






























              7















              So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.




              Well, not all use mode programs can, only those with the appropriate privileges. And that's determined by the kernel.



              /dev/mem is protected by the usual filesystem access permissions, and the CAP_SYS_RAWIO capability. iopl() and ioperm() are also restricted through the same capability.



              /dev/mem can also be compiled out of the kernel altogether (CONFIG_DEVMEM).




              Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?




              Well, maybe. It depends on what you want privileged user-space processes to be able to do. User-space processes can also trash the whole hard drive if they have access to /dev/sda (or equivalent), even though that defeats the purpose of having a filesystem driver to handle storage access.



              (Then there's also the fact that iopl() works by utilizing the CPU privilege modes on i386, so it can't well be said to defeat their purpose.)






              share|improve this answer




























                7












                7








                7








                So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.




                Well, not all use mode programs can, only those with the appropriate privileges. And that's determined by the kernel.



                /dev/mem is protected by the usual filesystem access permissions, and the CAP_SYS_RAWIO capability. iopl() and ioperm() are also restricted through the same capability.



                /dev/mem can also be compiled out of the kernel altogether (CONFIG_DEVMEM).




                Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?




                Well, maybe. It depends on what you want privileged user-space processes to be able to do. User-space processes can also trash the whole hard drive if they have access to /dev/sda (or equivalent), even though that defeats the purpose of having a filesystem driver to handle storage access.



                (Then there's also the fact that iopl() works by utilizing the CPU privilege modes on i386, so it can't well be said to defeat their purpose.)






                share|improve this answer
















                So a user mode program in Linux can do most things (I think most things) that can be done in kernel mode.




                Well, not all use mode programs can, only those with the appropriate privileges. And that's determined by the kernel.



                /dev/mem is protected by the usual filesystem access permissions, and the CAP_SYS_RAWIO capability. iopl() and ioperm() are also restricted through the same capability.



                /dev/mem can also be compiled out of the kernel altogether (CONFIG_DEVMEM).




                Doesn't allowing a user mode program to have all this power defeats the purpose of having CPU modes?




                Well, maybe. It depends on what you want privileged user-space processes to be able to do. User-space processes can also trash the whole hard drive if they have access to /dev/sda (or equivalent), even though that defeats the purpose of having a filesystem driver to handle storage access.



                (Then there's also the fact that iopl() works by utilizing the CPU privilege modes on i386, so it can't well be said to defeat their purpose.)







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited 4 hours ago









                Stephen Kitt

                175k24400477




                175k24400477










                answered 5 hours ago









                ilkkachuilkkachu

                60.7k1098172




                60.7k1098172






















                    user341099 is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    user341099 is a new contributor. Be nice, and check out our Code of Conduct.













                    user341099 is a new contributor. Be nice, and check out our Code of Conduct.












                    user341099 is a new contributor. Be nice, and check out our Code of Conduct.
















                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505527%2fdoesnt-allowing-a-user-mode-program-to-access-kernel-space-memory-and-execute-t%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    GameSpot

                    日野市

                    Tu-95轟炸機