I obviously have a somewhat unusual experience, but the only Linux kernel bug I've run into worked like this: ...
11 bugs found | Edit Search | Change Columns |
as
ID Status Resolution Sev Product Comp▲ Assignee▲ Reporter Summary
3423 CLOS WORK nor Sisyphus syslogd legion egor Проблемы с запуском/остановом/перезапуском syslogd
3968 CLOS FIXE blo Sisyphus syslogd legion sergey.kovalyov kernel: sending to unix dgram socket blocks in syscall
8935 CLOS NOTA nor Sisyphus syslogd legion stalker process `syslogd' is using obsolete setsockopt SO_BSDCOMPAT
12401 CLOS WONT nor Sisyphus syslogd legion rom_as Множественный перезапуск syslogd на момент выполнения скрипта /etc/cron.daily/logrotate
16559 CLOS NOTA nor Sisyphus syslogd legion bga Double domain in remote hostnames
2790 CLOS FIXE blo Sisyphus syslogd legion raorn syslogd dies if logfile reaches 2G-1 limit
23179 CLOS WONT enh Sisyphus syslogd legion imz do not lookup hostnames (an option)
27868 CLOS WONT enh Sisyphus syslogd legion serpiph service-файл для syslog
28091 CLOS DUPL nor Sisyphus syslogd legion amike syslogd: Необходимо обеспечить совместимость службы с systemd
2556 CLOS NOTA min Sisyphus syslogd legion dlebkov Пользователю не отсылаются log-messages
2807 CLOS FIXE min Sisyphus syslogd legion pilot empty chroot jail

File a new bug in the "syslogd" component of the "Sisyphus" product