Doesn't allowing a user mode program to access kernel space memory and execute the IN and OUT instructions defeat the purpose of having CPU modes?Questions on Linux kernel internalsHigh memory (user space) and highmem (kernel space)What mode of memory at the time linux kernel was loaded?How is user space process/thread controlled by the operating systemGet quota usage information as non-privileged userRewrite a system call in userspaceWhere are “the kernel stack”, “Frames for C run-time startup functions”, and “Frame for main()” in the memory layout of a program?What's the use of having a kernel part in the virtual memory space of Linux processes?Linux Kernel Mode Vs User ModeCan a device driver that accesses an IO device directly run in user mode?

How to write a chaotic neutral protagonist and prevent my readers from thinking they are evil?

What's the 'present simple' form of the word "нашла́" in 3rd person singular female?

Is it possible that a question has only two answers?

Proving a statement about real numbers

Do cubics always have one real root?

Is this Paypal Github SDK reference really a dangerous site?

What do *foreign films* mean for an American?

Why does Solve lock up when trying to solve the quadratic equation with large integers?

Is it a Cyclops number? "Nobody" knows!

What do you call someone who likes to pick fights?

Why do phishing e-mails use faked e-mail addresses instead of the real one?

From an axiomatic set theoric approach why can we take uncountable unions?

This Alpine town?

I reported the illegal activity of my boss to his boss. My boss found out. Now I am being punished. What should I do?

The meaning of ‘otherwise’

Rationale to prefer local variables over instance variables?

Can't make sense of a paragraph from Lovecraft

Street obstacles in New Zealand

How exactly does an Ethernet collision happen in the cable, since nodes use different circuits for Tx and Rx?

Was it really inappropriate to write a pull request for the company I interviewed with?

How to resolve: Reviewer #1 says remove section X vs. Reviewer #2 says expand section X

MySQL importing CSV files really slow

When Schnorr signatures are part of Bitcoin will it be possible validate each block with only one signature validation?

How do we create new idioms and use them in a novel?



Doesn't allowing a user mode program to access kernel space memory and execute the IN and OUT instructions defeat the purpose of having CPU modes?


Questions on Linux kernel internalsHigh memory (user space) and highmem (kernel space)What mode of memory at the time linux kernel was loaded?How is user space process/thread controlled by the operating systemGet quota usage information as non-privileged userRewrite a system call in userspaceWhere are “the kernel stack”, “Frames for C run-time startup functions”, and “Frame for main()” in the memory layout of a program?What's the use of having a kernel part in the virtual memory space of Linux processes?Linux Kernel Mode Vs User ModeCan a device driver that accesses an IO device directly run in user mode?













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.
























    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.






















      1












      1








      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 1 hour ago









      ilkkachu

      60.6k1098172




      60.6k1098172






      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 2 hours ago









      user341099user341099

      61




      61




      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


















          2















          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









            2















            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





























              2















              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



























                2












                2








                2








                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 1 hour ago









                Stephen Kitt

                175k24400477




                175k24400477










                answered 1 hour ago









                ilkkachuilkkachu

                60.6k1098172




                60.6k1098172




















                    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







                    -linux

                    Popular posts from this blog

                    Mobil Contents History Mobil brands Former Mobil brands Lukoil transaction Mobil UK Mobil Australia Mobil New Zealand Mobil Greece Mobil in Japan Mobil in Canada Mobil Egypt See also References External links Navigation menuwww.mobil.com"Mobil Corporation"the original"Our Houston campus""Business & Finance: Socony-Vacuum Corp.""Popular Mechanics""Lubrite Technologies""Exxon Mobil campus 'clearly happening'""Toledo Blade - Google News Archive Search""The Lion and the Moose - How 2 Executives Pulled off the Biggest Merger Ever""ExxonMobil Press Release""Lubricants""Archived copy"the original"Mobil 1™ and Mobil Super™ motor oil and synthetic motor oil - Mobil™ Motor Oils""Mobil Delvac""Mobil Industrial website""The State of Competition in Gasoline Marketing: The Effects of Refiner Operations at Retail""Mobil Travel Guide to become Forbes Travel Guide""Hotel Rankings: Forbes Merges with Mobil"the original"Jamieson oil industry history""Mobil news""Caltex pumps for control""Watchdog blocks Caltex bid""Exxon Mobil sells service station network""Mobil Oil New Zealand Limited is New Zealand's oldest oil company, with predecessor companies having first established a presence in the country in 1896""ExxonMobil subsidiaries have a business history in New Zealand stretching back more than 120 years. We are involved in petroleum refining and distribution and the marketing of fuels, lubricants and chemical products""Archived copy"the original"Exxon Mobil to Sell Its Japanese Arm for $3.9 Billion""Gas station merger will end Esso and Mobil's long run in Japan""Esso moves to affiliate itself with PC Optimum, no longer Aeroplan, in loyalty point switch""Mobil brand of gas stations to launch in Canada after deal for 213 Loblaws-owned locations""Mobil Nears Completion of Rebranding 200 Loblaw Gas Stations""Learn about ExxonMobil's operations in Egypt""Petrol and Diesel Service Stations in Egypt - Mobil"Official websiteExxon Mobil corporate websiteMobil Industrial official websiteeeeeeeeDA04275022275790-40000 0001 0860 5061n82045453134887257134887257

                    Frič See also Navigation menuinternal link

                    Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant