Re: How can I fake a device ?

[EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, Iasen Kostov wrote: Hi, I want to know is there a way to call *_probe (for device driver) with fake (PCI) device that does not exists in the system ? First of all a cant find how "struct device" is declared (i've searched even the comp

Re: How can I fake a device ?

In message <[EMAIL PROTECTED]>, Iasen Kostov wrote: >>> Hi, >>>I want to know is there a way to call *_probe (for device driver) with >>>fake (PCI) device that does not exists in the system ? >>>First of all a cant find how "struct device" is declared (i've searched >>>even the compile/ dir) a

Re: How can I fake a device ?

[EMAIL PROTECTED] wrote: In message <[EMAIL PROTECTED]>, Iasen Kostov wrote: Hi, I want to know is there a way to call *_probe (for device driver) with fake (PCI) device that does not exists in the system ? First of all a cant find how "struct device" is declared (i've searched even the compi

Re: too late null checks

Andre Oppermann wrote: Did you run your entire tool on the FreeBSD tree or is this subset of the available tests and checks? It's a small sample of the larger whole. The whole thing isn't as interesting to look at yet, but I'm working on it. ___ [EMAIL

Re: Network Packet drops in FreeBSD 5.2.1

Anand Subramanian wrote: Hi All, I am using an Intel Celeron box (single CPU,1.7GHz, 495MB real and 472 MB avail memory, FreeBSD 5.2.1 #15 release), to run a daemon process which shares a circular queue/buffer with the kernel. The daemon drains objects off the front of the queue while the queue obj

[TEST] rewritten floppy driver

Please help test this rewrite of the floppy driver so it can qualify to get into 5.3. Can the PC98 coders please try to create a fdc_cbus.c so we can use the same driver on PC98 ? If anybody wants to play with 2.88M floppies, I belive I found at least one bug which would have prevented it from w

use after free bugs

these are results from running Coverity's analysis over Freebsd 4.10 kernel. two improper loops: if_ef.c:566 and atapi-all.c ng_socket.c: possible double free of resp 815 and 870, depending on caller context. is this possible? if_bfe.c: double call to bfe_release_resources will free lots of stu

malloc null bugs

Found during analysis with Coverity's tools. FreeBSD 4.10 atapi-cd.c, everywhere. I understand there was some question of not being to deal with failure gracefully in ata, but many of these are in functions like ioctl which can easily report errors. igmp.c:find_rti mii.c:mii_phy_probe. device_

off by one bounds

errors in freebsd 4.10 found by Coverity's analysis. awi_wep.c:awi_wep_setalgo, algo == sizeof svr4_signal.c:SVR4_NSIG one larger than TBLSIZ linprocfs_misc.c:linprocfs_doprocstatus, p_stat == sizeof ibcs2_msg.c:ibcs2_poll, fd == FD_SETSIZE if_ray.c:ray_rx_mgt_info, len == NWID_LEN ciss.c:ciss_cam_