This document is mailed to lkml regularly and will be modified
whenever new victim wishes to be listed in it or someone can
no longer devote his time to maintainer work.
If you want your entry added/updated/removed, contact me.
--
vda
------- cut here ------ cut here ------ cut here ------ cut here ------
So, you are new to Linux kernel hacking and want to submit a kernel bug
report or a patch but don't know how to do it and _where_ to report it?
Then save this file for future reference.
Preparing bug report:
=====================
Compile problems: report GCC output and result of "grep '^CONFIG_' .config"
Oops: decode it with ksymoops
Unkillable process: Alt-SysRq-T and ksymoops relevant part
Yes it means you should have ksymoops installed and tested,
which is easy to get wrong. I've done that too often.
More info in the FAQ at http://www.tux.org/lkml/
Sending bug report/patch:
=========================
* Some device drivers have active developers, try to contact them first.
* Otherwise find a subsystem maintainer to which your report pertains
and send report to his address.
* Small fixes and device driver updates are best directed to subsystem
maintainers and "small bits" integrators.
* It never hurts to CC: Linux kernel mailing list, but without specific
maintainer address in To: field there is high probability that your
patch won't be noticed. You have been warned.
* Do not send it to all addresses at once! This will annoy lots of people
and isn't useful at all. It's a spam.
* Do NOT send small fixes to Linus, he just can't handle _everything_.
He will eventually receive it from maintainers/integrators, send it
their way.
* If your patch is something big and new, announce it on lkml and try
to attract testers. After it has been tested and discussed, you can
expect Linus to consider inclusion in mainline.
Current Linux kernel people
Note that this list is sorted in reversed date order, most recent
entries first. This means than entries at bottom can be outdated :-(
Linux kernel mailing list <[email protected]>
Post anything related to Linux kernel here, but nothing else :-)
Rogier Wolff <[email protected]> [12 mar 2002]
I do "specialix serial ports":
drivers/char/specialix.c (IO8+)
drivers/char/sx.c (SX, SI, SIO)
drivers/char/rio/*.c (RIO)
Martin Dalecki <[email protected]> [11 mar 2002]
IDE subsystem maintainer for 2.5
(mail Vojtech Pavlik <[email protected]> too)
Ed Vance <[email protected]> [05 mar 2002]
Maintainer for the generic serial driver, serial.c,
for 2.2 and 2.4 kernels. Please post patches to
[email protected] for tested bug
fixes or to add support for a new serial device.
Limited to time available. If I have not responded
in a week, yell at [email protected]
netfilter/iptables development <[email protected]> [23 feb 2002]
Please report all netfilter/iptables related problems
to this mailinglist, where all netfilter developers are present.
See also http://www.netfilter.org/contact.html
Hans Reiser <[email protected]> [16 feb 2002]
Send me all reiserfs related patches with a cc to
[email protected], send bug reports to
[email protected], send paid support requests to
[email protected] after going to http://www.namesys.com/support.html
to pay, send discussions (not bug reports unless they are
interesting to most persons) to [email protected].
If we sit on your patch for a week without responding,
yell at us, we deserve it. Look at our web page
at http://www.namesys.com for more about sending us code,
working with us, and our patch submission and tracking system.
Paul Bristow <[email protected]> [16 feb 2002]
I am an ide-floppy driver maintainer
(ATAPI ZIP, LS-120/240 Superdisk, Clik! drives).
Mike Phillips <[email protected]> [15 feb 2002]
Token ring subsystem and drivers.
Anton Altaparmakov <[email protected]> [15 feb 2002]
I am the NTFS guy.
https://bugzilla.redhat.com/bugzilla [14 feb 2002]
Reports of problems with the Red Hat shipped kernels.
Alan Cox <[email protected]> [14 feb 2002]
Linux 2.2 maintainer (maintenance fixes only).
Collator of patches for unmaintained things in 2.2/2.4.
Maintainer of the 2.4-ac (2.4 plus stuff being tested) tree.
I2O, sound, 3c501 maintainer for 2.2/2.4.
Robert Love <[email protected]> [14 feb 2002]
Preemptible kernel is mine.
ALSA development <[email protected]> [12 feb 2002]
Jaroslav Kysela <[email protected]> [12 feb 2002]
Advanced Linux Sound Architecture
ALSA patches are available at
ftp://ftp.alsa-project.org/pub/kernel-patches/*
Neil Brown <[email protected]> [08 feb 2002]
I am interested in any issues with the code in:
NFS server (fs/nfsd/*)
software RAID (drivers/md/{md,raid,linear}*)
or related include files.
Maksim Krasnyanskiy <[email protected]> [08 feb 2002]
I'm author and maintainer of the Bluetooth subsystem
and Universal TUN/TAP device driver.
These days mostly working on Bluetooth stuff.
Rik van Riel <[email protected]> [07 feb 2002]
Send me VM related stuff, please CC to [email protected]
Geert Uytterhoeven <[email protected]> [07 feb 2002]
I work on the frame buffer subsystem, the m68k port (Amiga part),
and the PPC port (CHRP LongTrail part).
Unfortunately I barely have spare time to really work on these
things. My job is not Linux-related (so far :-). I can not
promise anything about my maintainership performance.
H. Peter Anvin <[email protected]> [07 feb 2002]
i386 boot and feature code, i386 boot protocol, autofs3,
compressed iso9660 (but I'll accept all iso9660-related
changes.) kernel.org site manager; please contact me
for sponsorship-related issues.
kernel.org admins <[email protected]> [07 feb 2002]
Kernel.org sysadmins. Contact us if you notice something breaks,
or if you want a change make sure you give us at least 1-2 weeks.
Please note that we got a lot of feature requests, a lot of
which conflict or simply aren't practical; we don't have time to
respond to all requests.
Greg KH <[email protected]> [07 feb 2002]
I am USB and PCI Hotplug maintainer.
Trond Myklebust <[email protected]> [07 feb 2002]
I am NFS client maintainer.
James Simmons <[email protected]> [07 feb 2002]
Console and framebuffer sybsustems.
I also play around with the input layer.
Richard Gooch <[email protected]> [07 feb 2002]
I maintain devfs. I want people to Cc: me when reporting devfs
problems, since I don't read all messages on linux-kernel.
Send devfs related patches to me directly, rather than
bypassing me and sending to Linus/Marcelo/Alan/Dave etc.
Russell King <[email protected]> [06 feb 2002]
ARM architecture maintainer. Please send all ARM patches through
the patch system at http://www.arm.linux.org.uk/developer/patches/
New serial drivers maintainer for 2.5. Submit patches to
[email protected]
Andrew Morton <[email protected]> [05 feb 2002]
I'm receptive to any reproducible bug anywhere in the 2.4 kernel.
Specialising in ext2, ext3 and network drivers.
Not thinking about 2.5.x at this time.
Petr Vandrovec <[email protected]> [05 feb 2002]
ncpfs filesystem, matrox framebuffer driver, problems related
to VMware - in all of 2.2.x, 2.4.x and 2.5.x.
Reiserfs developers list <[email protected]> [05 feb 2002]
Send all reiserfs-related stuff here including but not limited to bug
reports, fixes, suggestions.
Oleg Drokin <[email protected]> [05 feb 2002]
SA11x0 USB-ethernet and SA11x0 watchdog are mine.
Vojtech Pavlik <[email protected]> [05 feb 2002]
Feel free to send me bug reports and patches to input device drivers
(drivers/input/*, drivers/char/joystick/*)
I also want to receive bug reports and patches for following
USB drivers: printer, acm, catc, hid*, usbmouse, usbkbd, wacom.
All other (not in the list) USB driver changes should go to USB
maintainer (hopefully there is one listed here :-).
Also CC me if you are posting VIA IDE driver related message
(although I am not IDE subsystem maintainer).
======= These entries are suggested by lkml folks ========
David S. Miller <[email protected]> [07 feb 2002]
I am Sparc64 and networking core maintainer.
======= These ones I made myself ========
======= I am waiting confirmation/correction from these people ========
Urban Widmark <[email protected]> [13 feb 2002]
smbfs
Jeff Garzik <[email protected]> [12 feb 2002]
I am the network-card-drivers guy (8139 for instance).
CC me and Andrew Morton <[email protected]> on network driver patches.
video4linux list <[email protected]> [12 feb 2002]
Gerd Knorr <[email protected]> [12 feb 2002]
video4linux
Tim Waugh <[email protected]> [08 feb 2002]
> Who is maintaining the linux iomega stuff?
For 2.4.x, me (in theory). I don't have time for 2.5.x at the moment.
Alexander Viro <[email protected]> [5 feb 2002]
I am NOT a fs subsystem maintainer. But I won't kill
you if you send me some generic fs bug reports and (hopefully) patches.
Andre Hedrick <[email protected]> [5 feb 2002]
I am IDE guy.
Andrea Arcangeli <[email protected]> [5 feb 2002]
Send VM related bug reports and patches to me.
Arnaldo Carvalho de Melo <[email protected]> [5 feb 2002]
NetBEIU, ....?
Dave Jones <[email protected]> [5 feb 2002]
I collect various bits and pieces for inclusion in 2.5,
espesially small and trivial ones and driver updates. Do not bother
Linus with them. I'll feed them to Linus when (and if) they
are proved to be worthy.
Eric S. Raymond <[email protected]> [5 feb 2002]
Send kernel configuration bug reports and suggestions to me.
Also I'll be more than happy to accept help enties for kernel config
options (Configure.help).
G?rard Roudier <[email protected]> [5 feb 2002]
I am SCSI guy.
Ingo Molnar <[email protected]> [5 feb 2002]
New scheduler in 2.5 and Tux are mine.
Jens Axboe <[email protected]> [5 feb 2002]
I am block device subsystem maintainer.
Keith Owens <[email protected]> [5 feb 2002]
ksymoops, kbuild, .. .. .. .. . are mine.
Linus Torvalds <[email protected]> [5 feb 2002]
Do not send anything to me unless it is for 2.5, well tested,
discussed on lkml and is used by significant number of people.
In general it is a bad idea to send me small fixes and driver
updates, send them to subsystem maintainers and/or
"small stuff" integrator (currently Dave Jones <[email protected]>,
see his entry). Sorry, I can't do everything.
Marcelo Tosatti <[email protected]> [5 feb 2002]
Do not send anything to me unless it is for 2.4 and well tested.
If you are sending me small fixes and driver updates, send
a copy to subsystem maintainers and/or "small stuff" integrators:
- Alan Cox <[email protected]>,
- Rusty Russell <[email protected]>.
Rusty Russell <[email protected]> [5 feb 2002]
> Here are some cleanups of whitespace in .....
Want me to add this to the trivial patch collection for tracking?
If so just send (or cc:) it to [email protected].
Please answer this e-mail with copy to me, for I am not subscribed to the
list.
I am debugging an Ethernet driver in the kernel 2.4.17, which is able to
recognize when the Ethernet link is up or down. When the link is up, I am
setting the bit IFF_RUNNING to the dev->flag parameter, and when it is down
this bit is reset. Besides this, I am calling the routines netif_carrier_on
and netif_carrier_off, respectively. This makes the interface status change
(when I call ifconfig eth0).
However, the routing table doesn't change when link goes up or down, though
they do change when I set the interface up and down. I couldn't find out what
I could do to make the Ethernet driver work in this way, so that the routes
to the Ethernet link would appear only if the interface was up and running.
Do you have an easy (or maybe difficult) way to do this? Any routine, any
magic?
Thanks in advance,
Helio Fujimoto.
On Mon, 4 Nov 2002, Helio Fujimoto wrote:
> Please answer this e-mail with copy to me, for I am not subscribed to the
> list.
>
> I am debugging an Ethernet driver in the kernel 2.4.17, which is able to
> recognize when the Ethernet link is up or down. When the link is up, I am
> setting the bit IFF_RUNNING to the dev->flag parameter, and when it is down
> this bit is reset. Besides this, I am calling the routines netif_carrier_on
> and netif_carrier_off, respectively. This makes the interface status change
> (when I call ifconfig eth0).
>
> However, the routing table doesn't change when link goes up or down, though
> they do change when I set the interface up and down. I couldn't find out what
> I could do to make the Ethernet driver work in this way, so that the routes
> to the Ethernet link would appear only if the interface was up and running.
> Do you have an easy (or maybe difficult) way to do this? Any routine, any
> magic?
>
> Thanks in advance,
>
> Helio Fujimoto.
>
User-mode code will reset the RTF_UP bit in the rt_flags member
of struct rtentry. This is the SIOCDELRT ioctl call. I have found
that, at least for 2.4.18 and previous, you need to delete any
previous route with the same parameters before setting any new one.
It seems that a default route ends up being set by merely setting
parameters for the interface.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
Bush : The Fourth Reich of America