Announcement

Collapse
No announcement yet.

Hardened Usercopy Appears Ready To Be Merged For Linux 4.8

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Hardened Usercopy Appears Ready To Be Merged For Linux 4.8

    Phoronix: Hardened Usercopy Appears Ready To Be Merged For Linux 4.8

    Yet another Linux kernel security feature coming to the mainline kernel that appears readied for the Linux 4.8 merge window is hardened usercopy...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    What was wrong with keeping this in GrSecurity? Did they not accept the change?

    Comment


    • #3
      Originally posted by fuzz View Post
      What was wrong with keeping this in GrSecurity? Did they not accept the change?
      What do you mean? The smaller diffset grsec has the better? Offloading small stuff into vanilla as acceptable size patchsets yields a more lightweight grsec and a select few nice things from grsec into vanilla Linux. Everybody wins.

      Comment


      • #4
        Originally posted by milkylainen View Post
        Everybody wins.
        Except grsec, but eh. I'm still pretty unsure why they haven't pushed harder for mainlining their code (disabled by default, enabled at user disgression).
        I seem to remember that they had issues with pluggable security modules thingy, but quite a bit of their code could be merged with vanilla behind few #ifdefs (okay, considerable ammount but still). Problem is probably politics, not code itself.

        Comment


        • #5
          Originally posted by milkylainen View Post
          What do you mean? The smaller diffset grsec has the better? Offloading small stuff into vanilla as acceptable size patchsets yields a more lightweight grsec and a select few nice things from grsec into vanilla Linux. Everybody wins.
          Sure, but that begs the question... why wasn't it in vanilla in the first place?

          Comment


          • #6
            Originally posted by fuzz View Post

            Sure, but that begs the question... why wasn't it in vanilla in the first place?
            Extra code in the kernel seems to add bloat even if it's disabled in the config.

            Comment


            • #7
              Originally posted by caligula View Post

              Extra code in the kernel seems to add bloat even if it's disabled in the config.
              In most cases when a feature is disabled in Kconfig it means the module(s) for the feature is/are not built or added into the compiled kernel image if it is a builtin kernel feature, so not necessarily adding bloat.

              Comment


              • #8
                Regardless... I'm happy to see it mainlined . Hope we can do the same with more security patches!

                Comment


                • #9
                  Originally posted by caligula View Post

                  Extra code in the kernel seems to add bloat even if it's disabled in the config.
                  Unfortunately, you're spot on with that comment. It is one of my major gripes with the Linux kernel.
                  Ie. The sheer amount of pork the kernel carries around that you just can't loose anymore.
                  A plain embedded kernel with absolutely zero features just besides running _this_ hardware and running a userspace is 100-200% larger than a fully functional late 2.6.x for example (which does the job).
                  Even if you disable everything besides mandatory drivers the kernel still is way, way fatter than it needs to be.

                  Comment


                  • #10
                    Originally posted by DeepDayze View Post

                    In most cases when a feature is disabled in Kconfig it means the module(s) for the feature is/are not built or added into the compiled kernel image if it is a builtin kernel feature, so not necessarily adding bloat.
                    Yes, the module isn't, but the other parts of the kernel had to be modified to make them compatible with this new feature. The kernel size is growing steadily even if you say N in the menuconfig.

                    Comment

                    Working...
                    X