optimized kernel/exit.c by adding NAGIEV #1261

gmehdiev · 2025-06-08T19:48:42Z

optimized kernel/exit.c by adding NAGIEV

ГОЙДА

KernelPRBot · 2025-06-08T19:50:10Z

Thanks for your contribution to the Linux kernel!

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process.

Here's what to do:

Format your contribution according to kernel requirements
Decide who to send your contribution to
Set up your system to send your contribution as an email
Send your contribution and wait for feedback

How do I format my contribution?

The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations.

Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea.

You can create patches with git format-patch.

Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary.

Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with.

Both of these are documented in the Submitting Patches documentation that is part of the kernel.

Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this.

Where do I send my contribution?

The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes.

If you don't already know what subsystem your change belongs to, the get_maintainer.pl script in the kernel source can help you.

get_maintainer.pl will take the patch or patches you created in the previous step, and tell you who is responsible for them, and what mailing lists are used. You can also take a look at the MAINTAINERS file by hand.

Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches.

It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.)

How do I send my contribution?

Use git send-email, which will ensure that your patches are formatted in the standard manner. In order to use git send-email, you'll need to configure git to use your SMTP email server.

For more information about using git send-email, look at the Git documentation or type git help send-email. There are a number of useful guides and tutorials about git send-email that can be found on the internet.

How do I get help if I'm stuck?

Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed.

Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine.

If you can't find an answer, there are a few places you can turn:

Kernel Newbies - this website contains a lot of useful resources for new kernel developers.
The kernel documentation - see also the Documentation directory in the kernel tree.

If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers!

I sent my patch - now what?

You wait.

You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at.

Then, you keep waiting. Three things may happen:

You might get a response to your email. Often these will be comments, which may require you to make changes to your patch, or explain why your way is the best way. You should respond to these comments, and you may need to submit another revision of your patch to address the issues raised.
Your patch might be merged into the subsystem tree. Code that becomes part of Linux isn't merged into the main repository straight away - it first goes into the subsystem tree, which is managed by the subsystem maintainer. It is then batched up with a number of other changes sent to Linus for inclusion. (This process is described in some detail in the kernel development process guide).
Your patch might be ignored completely. This happens sometimes - don't take it personally. Here's what to do:
- Wait a bit more - patches often take several weeks to get a response; more if they were sent at a busy time.
- Kernel developers often silently ignore patches that break the rules. Check for obvious violations of the Submitting Patches guidelines, the style guidelines, and any other documentation you can find about your subsystem. Check that you're sending your patch to the right place.
- Try again later. When you resend it, don't add angry commentary, as that will get your patch ignored. It might also get you silently blacklisted.

Further information

Working with the kernel development community - the official documentation for new kernel contributors

Happy hacking!

This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot.

quthery · 2025-06-10T15:48:41Z

брат спасибо большое тебе

AlexBSoft · 2025-06-10T15:51:42Z

We need it to be merged asap

brightkill · 2025-06-10T17:32:21Z

this MUST be merged

xi816 · 2025-06-11T20:24:50Z

герой

thehaffk

digital footprint

just-geniuss

Approved

devitq

LGTM, APPROVE ASAP

pablushaa

это шедевр

Confierka · 2025-06-11T20:31:43Z

Легенда

lina-torovoltas

LGTM

Lomasterrrr · 2025-06-11T20:33:56Z

aeeee

KiberPerdun · 2025-06-11T20:34:02Z

aeeee

horoni · 2025-06-11T20:34:54Z

аеееееее

foreA-adoxid · 2025-06-11T20:36:21Z

бесподобно

CHEYSOFF · 2025-06-11T20:48:55Z

lgtm

anatolygg · 2025-06-11T20:54:01Z

Approved

Ivanvet31 · 2025-06-11T21:05:22Z

аееее

bushkovsky · 2025-06-11T21:08:46Z

Best part of os

S-o-K-o-L

Здравствуй, небо в облаках,
Здравствуй, юность в сапогах!
Пропади, моя тоска,
Вот он я, привет, войска!

Эх, рельсы-поезда,
Как я попал сюда?

Здесь не то что на гражданке,
На какой-нибудь гражданке,
Жизнь снаружи и с изнанки
Сам попробуй изучи.
Для печали нет причин.

Непросто быть собой,
Когда шагает строй.

Только сердце птицей бьётся,
И ликует, и смеётся,
И ему не удаётся
Под конвоем петь в груди.
Знать бы, что там впереди.

Где-то течёт река,
Где-то дом, где всё ждут нас назад.
Это не грусть слегка,

Просто ветер щекочет глаза.

Где-то течёт река,
Где-то дом, где всё ждут нас назад.
Это не грусть слегка,
Просто ветер щекочет глаза.

Шаг вперёд и два назад,
Кто бы знал, чему я рад?
Просто сбросил я печаль
Словно голову с плеча.

На стыках рельсов путь,
Виски вбивает пульс.

Ты поймёшь, как будет нужно,
Где предательство, где дружба,
Где карьера, а где служба,
И как сердце безоружно,

Как обманчива наружность,
Сколько звёзд и сколько лычек,
Сколько лиц, личин, обличий,
И как мало в нас различий.

xi816

отлично

vberezhnev · 2025-06-17T14:13:29Z

кто нелох -- аппрувает PR

gmehdiev · 2025-06-18T11:04:40Z

@quenbyako

On a positive note, it’s helpful that all activity on GitHub is immutable. Every comment and approval is logged forever for all to see, becoming a permanent part of the project's history. 😉

So, a special thanks to everyone who cheered this on. By publicly supporting this disruption, you've voluntarily added yourselves to a very useful blocklist. This makes it trivial to identify users whose future contributions can be preemptively disregarded. Great job 👏

терпи

InternalHellhound · 2025-06-18T11:29:47Z

@quenbyako

On a positive note, it’s helpful that all activity on GitHub is immutable. Every comment and approval is logged forever for all to see, becoming a permanent part of the project's history. 😉
So, a special thanks to everyone who cheered this on. By publicly supporting this disruption, you've voluntarily added yourselves to a very useful blocklist. This makes it trivial to identify users whose future contributions can be preemptively disregarded. Great job 👏

терпи

Когда язык жестов в ядро добавишь?

gmehdiev · 2025-06-18T11:38:58Z

@quenbyako

On a positive note, it’s helpful that all activity on GitHub is immutable. Every comment and approval is logged forever for all to see, becoming a permanent part of the project's history. 😉
So, a special thanks to everyone who cheered this on. By publicly supporting this disruption, you've voluntarily added yourselves to a very useful blocklist. This makes it trivial to identify users whose future contributions can be preemptively disregarded. Great job 👏

терпи

    [
      
        ![selfish-soyjak](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
      
    ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
    
    
      
        
          
        
        
          
          
        
      
      [
        
          
        
      ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
    
   [ ![selfish-soyjak](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4) ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
  
    [
      
        ![selfish-soyjak](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
      
    ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
    
    
      
        
          
        
        
          
          
        
      
      [
        
          
        
      ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)
    
   [ ](https://private-user-images.githubusercontent.com/81379032/456471896-2f444509-cfbd-40ba-a257-f09db30bcaef.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTAyNDY0MTEsIm5iZiI6MTc1MDI0NjExMSwicGF0aCI6Ii84MTM3OTAzMi80NTY0NzE4OTYtMmY0NDQ1MDktY2ZiZC00MGJhLWEyNTctZjA5ZGIzMGJjYWVmLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNjE4VDExMjgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ0Y2JlZjk1YTg2NGUwYTEzNzFiMjFlNjQzMWZhNDFjYWNkMTRiZjA4ZmFiODc1NWE2YTY1MDhjMDQxMzUxZDUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.dC-BFOIjxyOX8EyaUXrCuFPK7Vafc9rZBNDVjrLO5a4)

Когда язык жестов в ядро добавишь?

После того как примут этот пр

devitq · 2025-06-18T19:00:32Z

@quenbyako

On a positive note, it’s helpful that all activity on GitHub is immutable. Every comment and approval is logged forever for all to see, becoming a permanent part of the project's history. 😉

So, a special thanks to everyone who cheered this on. By publicly supporting this disruption, you've voluntarily added yourselves to a very useful blocklist. This makes it trivial to identify users whose future contributions can be preemptively disregarded. Great job 👏

are u an idiot?

hlnmplus · 2025-06-18T19:03:25Z

Perfect

NZverkov · 2025-06-20T11:13:14Z

README

-There are several guides for kernel developers and users. These guides can
-be rendered in a number of formats, like HTML and PDF. Please read
-Documentation/admin-guide/README.rst first.
+[Куплет 1]


Слава Богу Z🙏❤️СЛАВА Z🙏❤️АНГЕЛА ХРАНИТЕЛЯ Z КАЖДОМУ ИЗ ВАС🙏❤️БОЖЕ ХРАНИ Z🙏❤️СПАСИБО ВАМ НАШИ СВО🙏🏻🇷🇺ХРАНИ ZOV✊🇷🇺💯СПАСИБО НАШИМ БОЙЦАМ

Слава Богу Z🙏❤️СЛАВА Z🙏❤️АНГЕЛА ХРАНИТЕ

Km1zZzoU · 2025-06-20T15:52:27Z

LGTM!!!

Kinderfeld · 2025-06-20T22:34:32Z

pure copium

BenzoiTheCoder · 2025-06-21T11:34:33Z

@quenbyako

On a positive note, it’s helpful that all activity on GitHub is immutable. Every comment and approval is logged forever for all to see, becoming a permanent part of the project's history. 😉
So, a special thanks to everyone who cheered this on. By publicly supporting this disruption, you've voluntarily added yourselves to a very useful blocklist. This makes it trivial to identify users whose future contributions can be preemptively disregarded. Great job 👏

are u an idiot?

Probably

rinkasumi · 2025-06-21T14:33:38Z

нихуйно

0z0sk0 · 2025-06-22T16:57:53Z

погодите, это LGTMиально?

dcq01

Hi! I'm a grad student working on a research project about using large language models to automate code review. Based on your commit 4f4ece9 and the changes in kernel/exit.c, my tool generated this comment:

Race Conditions: Implement appropriate locking mechanisms in any new code to ensure that shared resources are protected from concurrent access.
Signal Handling: Reintroduce robust signal handling to ensure that signals are properly managed during process exits, preventing potential denial of service or resource leaks.
Data Integrity: Ensure that any new code maintains the integrity of process states and implements checks to prevent inconsistent states.
Error Handling: Implement comprehensive error handling in the new code to ensure that all potential error conditions are addressed.
Input Validation: Include input validation checks in any new user-facing code to mitigate security risks.
Memory Management: Ensure that any new code that replaces functions like release_task() and exit_mm() includes proper memory cleanup for task structures and associated resources to prevent memory leaks.
Conduct Thorough Testing: Ensure that the new implementation is tested under various scenarios to validate its correctness and stability.
Test Coverage for Removed Code: Verify that the remaining functionality is still covered by existing tests. Review the test suite to ensure that all critical paths related to process management, exit handling, and signal processing are still being tested.
New Functionality: If any new functionality has been introduced or existing functionality has been modified, corresponding tests should be added.
Edge Cases: Pay special attention to edge cases that may arise from the removal of code. Ensure that the tests cover scenarios where specific error handling or cleanup routines might have been relevant.
Performance Testing: If the removed code was related to performance optimizations or resource management, consider adding performance tests to ensure that the changes do not introduce regressions in performance.
Reassess the Removal: Consider whether all the removed code is necessary. If certain functionalities are no longer needed, it may be better to refactor rather than remove them entirely.
Implement Replacement Logic: If the intention is to replace the existing functionality, ensure that the new implementation is robust and covers all necessary cases.
Logging on Process Exit: Add logging statements in the do_exit and release_task functions to log when a process exits, including its PID and exit code.
Audit and Logging: Reintroduce logging and auditing mechanisms to maintain visibility into process management activities.
Assertions for Critical States: In functions like __exit_signal, add assertions to ensure that the task being exited is in a valid state.
Error Handling and Logging: In functions where errors can occur (e.g., do_wait, kernel_waitid), log the error conditions.
Tracepoints: Consider adding tracepoints for key events such as process creation, exit, and state changes.
Consistency Checks: Add consistency checks before and after critical operations (like modifying task states).
Reintroduce Modular Functions: Restore the original functions and structures that were removed. Ensure that they are modular and well-defined to allow for easy extensions in the future.
Maintain Code Structure: Ensure that the code maintains a clear and logical structure. Group related functions together and use consistent naming conventions.
Documentation of Tests: Ensure that any tests added or modified are well-documented, explaining the purpose of the tests and what functionality they are verifying.

As part of my research, I'm trying to understand how useful these comments are in real-world development. If you have a moment, I'd be super grateful if you could quickly reply to these two yes/no questions:

Does this comment provide suggestions from a dimension you hadn’t considered?
1. Do you find this comment helpful?

Thanks a lot for your time and feedback! And sorry again if this message is a bother.

yoann256 · 2025-06-25T16:25:00Z

Hi! I'm a grad student working on a research project about using large language models to automate code review. Based on your commit 4f4ece9 and the changes in kernel/exit.c, my tool generated this comment:

Race Conditions: Implement appropriate locking mechanisms in any new code to ensure that shared resources are protected from concurrent access.

Signal Handling: Reintroduce robust signal handling to ensure that signals are properly managed during process exits, preventing potential denial of service or resource leaks.

Data Integrity: Ensure that any new code maintains the integrity of process states and implements checks to prevent inconsistent states.

Error Handling: Implement comprehensive error handling in the new code to ensure that all potential error conditions are addressed.

Input Validation: Include input validation checks in any new user-facing code to mitigate security risks.

Memory Management: Ensure that any new code that replaces functions like release_task() and exit_mm() includes proper memory cleanup for task structures and associated resources to prevent memory leaks.

Conduct Thorough Testing: Ensure that the new implementation is tested under various scenarios to validate its correctness and stability.

Test Coverage for Removed Code: Verify that the remaining functionality is still covered by existing tests. Review the test suite to ensure that all critical paths related to process management, exit handling, and signal processing are still being tested.

New Functionality: If any new functionality has been introduced or existing functionality has been modified, corresponding tests should be added.

Edge Cases: Pay special attention to edge cases that may arise from the removal of code. Ensure that the tests cover scenarios where specific error handling or cleanup routines might have been relevant.

Performance Testing: If the removed code was related to performance optimizations or resource management, consider adding performance tests to ensure that the changes do not introduce regressions in performance.

Reassess the Removal: Consider whether all the removed code is necessary. If certain functionalities are no longer needed, it may be better to refactor rather than remove them entirely.

Implement Replacement Logic: If the intention is to replace the existing functionality, ensure that the new implementation is robust and covers all necessary cases.

Logging on Process Exit: Add logging statements in the do_exit and release_task functions to log when a process exits, including its PID and exit code.

Audit and Logging: Reintroduce logging and auditing mechanisms to maintain visibility into process management activities.

Assertions for Critical States: In functions like __exit_signal, add assertions to ensure that the task being exited is in a valid state.

Error Handling and Logging: In functions where errors can occur (e.g., do_wait, kernel_waitid), log the error conditions.

Tracepoints: Consider adding tracepoints for key events such as process creation, exit, and state changes.

Consistency Checks: Add consistency checks before and after critical operations (like modifying task states).

Reintroduce Modular Functions: Restore the original functions and structures that were removed. Ensure that they are modular and well-defined to allow for easy extensions in the future.

Maintain Code Structure: Ensure that the code maintains a clear and logical structure. Group related functions together and use consistent naming conventions.

Documentation of Tests: Ensure that any tests added or modified are well-documented, explaining the purpose of the tests and what functionality they are verifying.

As part of my research, I'm trying to understand how useful these comments are in real-world development. If you have a moment, I'd be super grateful if you could quickly reply to these two yes/no questions:

Does this comment provide suggestions from a dimension you hadn’t considered?

Do you find this comment helpful?

Thanks a lot for your time and feedback! And sorry again if this message is a bother.

ai moment

EldarKusdavletov

LGTM

M4ddCat · 2025-06-26T06:35:28Z

Linux kernel need realy good practices like this.

M4ddCat

Better than rust parts

demndevel · 2025-06-27T20:48:07Z

крутое

Mtfl0n · 2025-07-09T16:26:37Z

только благодаря таким изменениям ядро будет процветать

unixource · 2025-07-15T15:42:13Z

amitabhakarmakar · 2025-07-15T15:45:24Z

unsubscribe

…

On Tue, Jul 15, 2025 at 11:44 AM unixource ***@***.***> wrote: *unixource* left a comment (torvalds/linux#1261) <#1261 (comment)> default.png (view on web) <https://github.com/user-attachments/assets/f198842e-988e-4210-92d3-c10f8fc99c2e> default.png (view on web) <https://github.com/user-attachments/assets/47ce30db-d652-4096-868e-f87174c04e03> — Reply to this email directly, view it on GitHub <#1261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXQRFLSY4FVSB2AGFWTMWD3IUOV7AVCNFSM6AAAAAB63OIO3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANZUGE4TSMJWGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Thanks, Amitabha Karmakar.

gmehdiev added 3 commits May 8, 2024 13:05

Add braille

27e4952

Update README

dc890bc

ГОЙДА

Update exit.c

4f4ece9

wavy-cat approved these changes Jun 11, 2025

View reviewed changes

thehaffk approved these changes Jun 11, 2025

View reviewed changes

just-geniuss approved these changes Jun 11, 2025

View reviewed changes

devitq approved these changes Jun 11, 2025

View reviewed changes

pablushaa approved these changes Jun 11, 2025

View reviewed changes

lina-torovoltas approved these changes Jun 11, 2025

View reviewed changes

horoni approved these changes Jun 11, 2025

View reviewed changes

Lsc0x80 approved these changes Jun 11, 2025

View reviewed changes

CHEYSOFF approved these changes Jun 11, 2025

View reviewed changes

hencsat46 approved these changes Jun 11, 2025

View reviewed changes

S-o-K-o-L approved these changes Jun 11, 2025

View reviewed changes

vovan12361 approved these changes Jun 11, 2025

View reviewed changes

xi816 approved these changes Jun 11, 2025

View reviewed changes

Kinok0Bash approved these changes Jun 18, 2025

View reviewed changes

hlnmplus approved these changes Jun 18, 2025

View reviewed changes

NZverkov reviewed Jun 20, 2025

View reviewed changes

zaitsev726 approved these changes Jun 25, 2025

View reviewed changes

shaawrk approved these changes Jun 25, 2025

View reviewed changes

dcq01 reviewed Jun 25, 2025

View reviewed changes

EldarKusdavletov approved these changes Jun 25, 2025

View reviewed changes

M4ddCat approved these changes Jun 26, 2025

View reviewed changes

Teishotoku approved these changes Jun 27, 2025

View reviewed changes

agvantibo-again approved these changes Jul 6, 2025

View reviewed changes

Wokzy approved these changes Jul 14, 2025

View reviewed changes

wavy-cat approved these changes Jul 15, 2025

View reviewed changes

optimized kernel/exit.c by adding NAGIEV #1261

Are you sure you want to change the base?

optimized kernel/exit.c by adding NAGIEV #1261

Conversation

gmehdiev commented Jun 8, 2025

Uh oh!

KernelPRBot commented Jun 8, 2025

How do I format my contribution?

Where do I send my contribution?

How do I send my contribution?

How do I get help if I'm stuck?

I sent my patch - now what?

Further information

Uh oh!

quthery commented Jun 10, 2025

Uh oh!

AlexBSoft commented Jun 10, 2025

Uh oh!

brightkill commented Jun 10, 2025

Uh oh!

xi816 commented Jun 11, 2025

Uh oh!

thehaffk left a comment

Choose a reason for hiding this comment

Uh oh!

just-geniuss left a comment

Choose a reason for hiding this comment

Uh oh!

devitq left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pablushaa left a comment

Choose a reason for hiding this comment

Uh oh!

Confierka commented Jun 11, 2025

Uh oh!

lina-torovoltas left a comment

Choose a reason for hiding this comment

Uh oh!

Lomasterrrr commented Jun 11, 2025

Uh oh!

KiberPerdun commented Jun 11, 2025

Uh oh!

horoni commented Jun 11, 2025

Uh oh!

foreA-adoxid commented Jun 11, 2025

Uh oh!

CHEYSOFF commented Jun 11, 2025

Uh oh!

anatolygg commented Jun 11, 2025

Uh oh!

Ivanvet31 commented Jun 11, 2025

Uh oh!

bushkovsky commented Jun 11, 2025

Uh oh!

S-o-K-o-L left a comment

Choose a reason for hiding this comment

Uh oh!

xi816 left a comment

Choose a reason for hiding this comment

Uh oh!

vberezhnev commented Jun 17, 2025

Uh oh!

gmehdiev commented Jun 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

InternalHellhound commented Jun 18, 2025

Uh oh!

gmehdiev commented Jun 18, 2025

Uh oh!

devitq commented Jun 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hlnmplus commented Jun 18, 2025

Uh oh!

NZverkov Jun 20, 2025

Choose a reason for hiding this comment

Uh oh!

Km1zZzoU commented Jun 20, 2025

devitq left a comment •

edited

Loading

gmehdiev commented Jun 18, 2025 •

edited

Loading

devitq commented Jun 18, 2025 •

edited

Loading