GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Greg K-H (gregkh@social.kernel.org)

  1. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Thursday, 27-Feb-2025 02:36:26 JST Greg K-H Greg K-H
    Perl is now a CNA, able to assign their own CVE ids, this is great news!
    https://security.metacpan.org/2025/02/25/cpansec-is-cna-for-perl-and-cpan.html

    Just in time for my talk about this very topic in a few weeks about how all open source projects should be doing this:
    https://lfms25.sched.com/event/1urXE/take-control-over-your-projects-cve-entries-before-someone-else-does-greg-kroah-hartman-linux-foundation
    In conversation about a month ago from social.kernel.org permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      CPANSec is CNA for Perl and the CPAN ecosystem
      from Stig Palmquist, Timothy Legge and Breno G. de Oliveira
      The CPAN Security Group was authorized by the CVE Program as a CVE Numbering Authority (CNA) on Feb 25, 2025. A CNA assigns and manages CVE identifiers for projects in their scope.
    2. Domain not in remote thumbnail source whitelist: lfms25.sched.com
      The Linux Foundation Member Summit 2025: Take Control Over Your Project's CVE Ent...
      View more about this event at The Linux Foundation Member Summit 2025
  2. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Saturday, 15-Feb-2025 06:48:31 JST Greg K-H Greg K-H
    While I don't know if is the first time this has happened, it's good to acknowledge this given all the crazy, odd, and incorrect press about Rust in Linux these days.

    A new in-kernel api just landed in linux-next from my tree and should hopefully show up in 6.14 to make some kinds of drivers easier to write, that has a rust binding added at the exact same time:
    https://lore.kernel.org/all/2025021023-sandstorm-precise-9f5d@gregkh/

    Many thanks to Lyude and Danilo and many other Rust kernel developers for the help in creating the binding and make the C side work well for both Rust and C code at the same time. The end result here for any C developer alone, is much better off for all of their help.
    In conversation about a month ago from social.kernel.org permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      [PATCH v4 0/9] Driver core: Add faux bus devices - Greg Kroah-Hartman
  3. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Tuesday, 28-Jan-2025 15:09:36 JST Greg K-H Greg K-H
    in reply to
    • daniel:// stenberg://
    @bagder Oh crap, yes, that does work on this model! It's even buried on the spec sheet if you read it close enough. It didn't on a previous model I had, so I'll blame that reason why I never tried this out. Ok, one less cable to carry around with me when traveling now, thanks!
    In conversation about 2 months ago from social.kernel.org permalink
  4. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Monday, 27-Jan-2025 22:11:04 JST Greg K-H Greg K-H
    Scariest cable I have that I actually use. It's a USB-C to Thinkpad "adapter" that I bought to power a thinkpad that shipped with a giant 135W brick-of-a-power-supply. This cable does work, but has the tendency to "overload" many USB chargers, causing them to reset. Fun times, but good for traveling so I don't have to lug the brick around with me as well.
    In conversation about 2 months ago from social.kernel.org permalink

    Attachments


    1. https://media.social.kernel.org/media/6f7f936f6cc23c13cf4f5862d2c7555dce2627cf7d5df9682c063d9af11d4ba8.png
  5. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Tuesday, 21-Jan-2025 00:28:22 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    • Alan Jenkins
    @alwayscurious @sima @sourcejedi That's one reason, the other one was "power just glitched, my printer better be on the same device node it was before it was turned off". Same for keyboards, mice, disks, etc.
    In conversation about 2 months ago from social.kernel.org permalink
  6. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Tuesday, 21-Jan-2025 00:27:37 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    @alwayscurious @sima "Normal" PCI hotplug systems should export this information, as the BIOS expects a user to add/remove PCI devices on a slot basis. Otherwise why would a BIOS care about exporting the slot number at all. So it's not required, and you are lucky if it shows up. good luck!
    In conversation about 2 months ago from social.kernel.org permalink
  7. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Friday, 17-Jan-2025 00:46:34 JST Greg K-H Greg K-H
    in reply to
    • Josh Bressers
    @joshbressers Linux is only #6? We better get on that to reclaim our 2nd ranked spot of last year despite only participating for 10 1/2 months, not the full 12 everyone else was able to have! :)
    In conversation about 2 months ago from social.kernel.org permalink
  8. Embed this notice
    daniel:// stenberg:// (bagder@mastodon.social)'s status on Thursday, 16-Jan-2025 20:00:20 JST daniel:// stenberg:// daniel:// stenberg://

    #curl has been a CNA for a year now https://daniel.haxx.se/blog/2024/01/16/curl-is-a-cna/

    In conversation about 3 months ago from mastodon.social permalink Repeated by gregkh

    Attachments

    1. Domain not in remote thumbnail source whitelist: daniel.haxx.se
      curl is a CNA
      from Daniel Stenberg
      The curl project has been accepted as a CVE Numbering Authority (CNA) for vulnerabilities in all products directly made or managed by the project. If I'm counting correctly, we are the 351st CNA. The official announcement from Mitre states: curl is now a CVE Numbering Authority (CNA) for all products made and managed by the … Continue reading curl is a CNA →
  9. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Wednesday, 15-Jan-2025 22:54:24 JST Greg K-H Greg K-H
    in reply to
    • K. Ryabitsev ????
    @monsieuricon I wish someone would tell me the steps for CVE repair for the kernel so we don't have to keep making them up as we go along :)
    In conversation about 3 months ago from social.kernel.org permalink
  10. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Monday, 13-Jan-2025 15:42:13 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    • Alan Jenkins
    @alwayscurious @sima @sourcejedi Again, reuse of major/minor numbers was a design requirement at the time. And, you know the path / label / metadata / whatever for the block device before you mount it, so go off of that information if you don't trust the device major/minor number information.
    In conversation about 3 months ago from social.kernel.org permalink
  11. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Monday, 13-Jan-2025 15:40:38 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    @alwayscurious @sima PCI devices, at the bus/slot/function level do not have device nodes, so I don't understand the issue here.

    They might have a specific PCI driver bound to them, at the function level, and if so, the parent of the device node for that class device (i.e. input, tty, drm, etc.) will then point to that PCI function. But PCI slots don't always match up to PCI bus and device numbers either, as that's a physical thing and many PCI systems don't expose or even know that information (i.e. the BIOS doesn't know.)

    Also, PCI bus numbers can change at boot, so you can't know what is happening.

    Driver probing can be deferred at any time by userspace for USB devices, and I think that was recently added for PCI devices too, look for the "trusted" device information in the documentation somewhere.

    Good luck!
    In conversation about 3 months ago from social.kernel.org permalink
  12. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Sunday, 12-Jan-2025 18:46:58 JST Greg K-H Greg K-H
    in reply to
    • Aho
    @aho Thanks for the info, I'll look into it when I get a chance! I've fixed my original problem for now, so odds are I'll live with it until something breaks again.
    In conversation about 3 months ago from social.kernel.org permalink
  13. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Sunday, 12-Jan-2025 18:45:56 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    • Alan Jenkins
    @alwayscurious @sima @sourcejedi That ship sailed decades ago as we had to support device node reuse a long time ago, it was a requirement! But obviously not your requirement :)

    You have full control over device node creation in userspace, that's what udev gives you if you want (or any udev-like program). set up a whole different /dev/ with just your naming/numbering scheme. The kernel gives you the interface and the information to do this, why not take advantage of it if you need it?
    In conversation about 3 months ago from social.kernel.org permalink
  14. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Sunday, 12-Jan-2025 18:42:32 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Demi Marie Obenour
    @alwayscurious @sima Then do that,the kernel provides you this information through sysfs, that is what it was explicitly designed for.

    But yes, the race condition of "parse the topology, determine the device node, and go to open it" when the device is removed and a different one added right between those last two steps is real. Luckily in real-hardware situations, almost extremely rare if not physically impossible due to hardware debounce times, and one that we explicitly did not care about when we created sysfs and udev (i.e. physical access trumps anything).
    In conversation about 3 months ago from social.kernel.org permalink
  15. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Thursday, 02-Jan-2025 18:09:17 JST Greg K-H Greg K-H
    New year, new hardware failure, must be time for a new motherboard, any recommendations of what the "best" AMD workstation motherboard is these days?
    In conversation about 3 months ago from social.kernel.org permalink

    Attachments


    1. https://media.social.kernel.org/media/ce31a0dc9ec6f4b03c13de54512cc2148f72d006521be68c3f256bec15b25b2f.png
  16. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Saturday, 21-Dec-2024 16:43:56 JST Greg K-H Greg K-H
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • 🐧sima🐧
    • Alan Jenkins
    @lanodan @sima @sourcejedi Ordering is never guaranteed stable.
    In conversation about 3 months ago from social.kernel.org permalink
  17. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Saturday, 21-Dec-2024 01:30:30 JST Greg K-H Greg K-H
    in reply to
    • 🐧sima🐧
    • Alan Jenkins
    @sourcejedi @sima Yeah, no blog posts, just loads of lkml emails over the years, sorry.

    That machine that randomly reassigned PCI ids at boot time is no longer with me, but it was great for testing. I'm sure you can do the same with virtual machines these days, passing in different virtual pci devices to them.

    Persistent naming is for userspace to handle, the kernel just uses "grab the next free number" as it's naming "policy" as that's all it can really do.
    In conversation about 3 months ago from social.kernel.org permalink
  18. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Thursday, 19-Dec-2024 16:18:07 JST Greg K-H Greg K-H
    in reply to
    • Vegard Nossum 🥑
    @vegard Does our current documentation not make this clear?

    If not, patches welcome :)
    In conversation about 3 months ago from social.kernel.org permalink
  19. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Thursday, 19-Dec-2024 16:13:59 JST Greg K-H Greg K-H
    in reply to
    • Vegard Nossum 🥑
    @vegard Yes, that would miss the normal "review all the stable commits" process. If you think there is a mainline-only commit that needs to have a CVE, please let us know at the cve@k.o address and we can assign it then.

    But better yet, backport the fix to stable and it all happens automatically for you :)
    In conversation about 3 months ago from social.kernel.org permalink
  20. Embed this notice
    Greg K-H (gregkh@social.kernel.org)'s status on Tuesday, 17-Dec-2024 18:08:41 JST Greg K-H Greg K-H
    in reply to
    • Thorsten Leemhuis (acct. 1/4)
    • Matthieu Baerts
    @matttbe @kernellogger Maybe, maybe not. Please see my old post here: http://www.kroah.com/log/blog/2021/02/03/helping-out-with-lts-kernel-releases/ for what drives all of this (hint, people actually asking that they need it AND providing the help to make it possible.)
    In conversation about 4 months ago from gnusocial.jp permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: www.kroah.com
      Helping Out With Lts Kernel Releases
      A recent email thread about “Why isn’t the 5.10 stable kernel listed as supported for 6 years yet!” on the linux-kernel mailing list ended up generating a bunch of direct emails to me asking what could different companies and individuals due to help out. What exactly was I looking for here? Instead of having to respond to private emails with the same information over and over, I figured it was better to just put it here so that everyone can see what exactly I am expecting with regards to support in order to be able to maintain a kernel for longer than 2 years:
  • Before

User actions

    Greg K-H

    Greg K-H

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          101452
          Member since
          24 Feb 2023
          Notices
          89
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.