TUZ が revertされました revert linux.conf.au 2009: tuz this reverts commit 8032b526d1a3bd91ad633dd3a3b5fdbc47ad54f1. hey, it was only meant to be a single release. now they can all die as far as i'm concerned. [ just kidding. they're cute and cuddly. except when they have horrible nasty facial diseases. oh, and i guess they're not actually that cuddly even when disease-free. ] signed-off-by: linus torvalds
[LKML] IRQF_SAMPLE_RANDOM question... robin getzが以下の質問をなげて although there was some discussion http://thread.gmane.org/gmane.linux.kernel/680723 about removing irqf_sample_random from the remaining network drivers in may of 2008, but they still appears to be there in 2.6.29. drivers/net/ibmlana.c drivers/net/macb.c drivers/net/3c523.c drivers/net/3c527.c drivers/net/netxen/netxen_nic_main.c drivers/net/cris/eth_v10.c drivers/net/xen-netfront.c drivers/net/atlx/atl1.c drivers/net/qla3xxx.c drivers/net/tg3.c drivers/net/niu.c so what is the plan? if i send a patch to add irqf_sample_random to others (like the blackfin) networking drivers - will it get rejected? we have lots of embedded headless systems (no keyboard/mouse, no soundcard, no video) systems with *no* sources of entropy - and people using ssl. i didn't really find any docs which describe what should have irqf_sample_random on it or not. i did find matt mackall describing it as: > we currently assume that irqf_sample_random means 'this is a completely > trusted unobservable entropy source' which is obviously wrong for > network devices but is right for some other classes of device. currently - i see most things i see using irqf_sample_random would also fail the completely unobservable test. other than the trng that are inside the cpu - what does pass? i can put a scope/analyser on a device - and look at the touchscreens, serial devices, usb, all without cracking the case. drivers/block/xen-blkfront.c: xen virtual block device frontend drivers/i2c/busses/i2c-pmcmsp.c: pmc msp twi/smbus/i2c driver drivers/input/keyboard/bf54x-keys.c: keypad driver for bf54x processors drivers/input/keyboard/gpio_keys.c: keyboard driver for cpu gpios drivers/input/serio/hp_sdc.c: hp i8042-based sdc driver drivers/input/touchscreen/wm97xx-core.c: wm97xx core - touch screen drivers/serial/mpc52xx_uart.c: freescale mpc52xx psc uart drivers/serial/uartlite.c: xilinx uartlite serial driver drivers/usb/gadget/omadrivers/usb/gadget/omap_udc omap udc driver if i want to get more intrusive (expensive) - i can look at spi, i2c, and other things that only might be observable at the pcb level (including things that are inside the chipset). what are the guidelines for including irqf_sample_random? thanks -robin -- to unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majordomo@vger.kernel.org more majordomo info at http://vger.kernel.org/majordomo-info.html please read the faq at http://www.tux.org/lkml/ jeff garzik が端的に説明
