Look into the netlabel and xfrm code. In Smack it gets dealt with in smack_lsm.c, but Smack only uses netlabel. SELinux spreads the handling into a number of files, including hooks.c, netlabel.c, xfrm.c, and ss/services.c. Casey Schaufler casey@schaufler-ca.com -

Hehe, I often do it that way myself, but just edit the subject of each mail and manually put in the [PATCH XX/YY] bit. It is just that sometimes mails get lost, so it's very nice to know how many patches to expect in a series :) -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html -

The encoding is set to ISO-2022-JP, this is probably breaking things. -- Cheers, Alistair. 137/1 Warrender Park Road, Edinburgh, UK. -

OK, I've got it figured out now. What happened is this -- alpine has this nifty feature that (if not explicitly set) it will automatically adjust the content-type encoding of outgoing mails depending upon the kind of text it sees written in the mail. Now when I normally post (eg. the first mail in this set), it naturally goes out as US-ASCII. What was special about the other mails was that each contained GCC's error/warning output. And if you've noticed it produces that totally pointless special...

The Marvell bridge chips used on HighPoint SATA cards do not seem to support the MWDMA modes (at least that caould be seen in their so-called drivers :-), so the driver needs to account for this -- to achieve this: - add mdma_filter() method from the original patch by Bartlomiej Zolnierkewicz with his consent, also adding the method callout to ide_rate_filter(); - installed the method for all chips to only return empty mask if a SATA drive is detected onHPT372{AN]/374 chips... Signed-off-by...

I decided to ruin my Sunday with an utterly pointless activity -- waging war on -mm build warnings. Some of the code I touched belonged to grotty, unused, dying drivers, but still, the end result was that I can now only see 5 warnings remaining on my typical .config (those have to do with pci_{find,enable}_device deprecation and __must_check on sysfs_create_{file,link} so I'll just leave 'em for now). Some were unused variable warnings, some uninitialized (few of those real bugs, but most not), s...

drivers/scsi/dc395x.c: In function $B!F(Jdc395x_init_one$B!G(J: drivers/scsi/dc395x.c:4272: warning: $B!F(Jptr$B!G(J may be used uninitialized in this function has been verified to be a bogus warning. Let's shut it up. Signed-off-by: Satyam Sharma <satyam@infradead.org> --- drivers/scsi/dc395x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-2.6.23-rc4-mm1/drivers/scsi/dc395x.c~fix 2007-09-02 20:57:51.000000000 +0530 +++ linux-2.6.23-rc4-mm1/drivers/scs...

I'll post the info as a reply to the first mail in this series. I have fairly recent gcc (4.1.1) and I don't see us dropping support for it in Well, uninitialized_var() is definitely more greppable than "= 0" which code all over does all the time :-) Anyway, the point is that the warnings are bogus anyway (hence maintainers Cc:'ed so that they can confirm if I arrived at the conclusion correctly) /and/ that uninitialized_var() stands out sorely, so I don't see bugs getting "hidden" at all -- ...

same comment as with the last uninit'd var patch: these markers should be used sparingly. Try it on multiple compiler versions, see if it's a new behavior. Quite realistically, you might actually be finding gcc bugs, implying the proper path is to file a gcc bug report (and they are _very_ diligent about handling these, its impressive) rather than to patch the Linux kernel. Overall, for any uninitialized_var() patch, we need more info on platform/compiler version/analysis methods/etc. ...

sound/isa/es18xx.c: In function $B!F(Jsnd_es18xx_isa_probe$B!G(J: sound/isa/es18xx.c:2251: warning: $B!F(Jerr$B!G(J may be used uninitialized in this function gcc is a sad, sad compiler. This warning is bogus so let's shut it up. Signed-off-by: Satyam Sharma <satyam@infradead.org> --- sound/isa/es18xx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) --- linux-2.6.23-rc4-mm1/sound/isa/es18xx.c~fix 2007-09-02 21:16:54.000000000 +0530 +++ linux-2.6.23-rc4-mm1/soun...

drivers/message/fusion/mptctl.c: In function $B!F(Jmptctl_mpt_command$B!G(J: drivers/message/fusion/mptctl.c:1764: warning: $B!F(JbufIn.len$B!G(J may be used uninitialized in this function drivers/message/fusion/mptctl.c:1765: warning: $B!F(JbufOut.len$B!G(J may be used uninitialized in this function come because gcc gets confused by some "goto" statements in above function. The warnings have been verified to be bogus, however, the function does initialize these later (after the offendi...

drivers/mmc/core/bus.c: In function $B!F(Jmmc_bus_uevent$B!G(J: drivers/mmc/core/bus.c:77: warning: unused variable $B!F(Jlength$B!G(J drivers/mmc/core/bus.c:77: warning: unused variable $B!F(Ji$B!G(J Signed-off-by: Satyam Sharma <satyam@infradead.org> --- drivers/mmc/core/bus.c | 1 - 1 file changed, 1 deletion(-) --- linux-2.6.23-rc4-mm1/drivers/mmc/core/bus.c~fix 2007-09-02 19:18:05.000000000 +0530 +++ linux-2.6.23-rc4-mm1/drivers/mmc/core/bus.c 2007-09-02 19:18:08...

Blah. Your message has: Content-Type: TEXT/PLAIN; charset=iso-2022-jp This apparently is caused by a combination of GCC using groovy UTF tickmarks in its error messages when in a UTF locale and alpine believing it to be a great idea to automatically try for the "simplest" character set it can encode the content in. No idea why that means that iso-2022-jp is picked, but it is. While I could actually read the message this time you should see what iso-2022-jp does to my font. It's scary. ...

drivers/scsi/ips.c: In function $B!F(Jips_register_scsi$B!G(J: drivers/scsi/ips.c:6869: warning: ignoring return value of $B!F(Jscsi_add_host$B!G(J, declared with attribute warn_unused_result scsi_add_host() is __must_check, so let's check it's return and cleanup appropriately on errors. Signed-off-by: Satyam Sharma <satyam@infradead.org> --- drivers/scsi/ips.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) --- linux-2.6.23-rc4-mm1/drivers/scsi/ips.c~fix 2...

> > drivers/scsi/ips.c: In function

drivers/usb/serial/bus.c: In function $B!F(Jusb_serial_bus_deregister$B!G(J: drivers/usb/serial/bus.c:185: warning: passing argument 1 of $B!F(Jfree_dynids$B!G(J from incompatible pointer type Above build warning comes when CONFIG_HOTPLUG=n because argument of free_dynids() in serial/bus.c is a struct usb_serial_driver, not a struct usb_driver. This is not a runtime bug, because the function is an empty stub and never dereferences the passed pointer anyway. Signed-off-by: Satyam Sharma ...

Looks good to me. The new style seems to be to do #ifdef SOMETHING code #else #define wiphy_uevent NULL #endif and then using it unconditionally, but I'm fine with both.

drivers/usb/misc/sisusbvga/sisusb.c: In function $B!F(Jusb_sisusb_init$B!G(J: drivers/usb/misc/sisusbvga/sisusb.c:3321: warning: unused variable $B!F(Jsisusb$B!G(J drivers/usb/misc/sisusbvga/sisusb.c:3320: warning: unused variable $B!F(Jretval$B!G(J are trivially solved by getting rid of the unused variables. drivers/usb/misc/sisusbvga/sisusb.c: In function $B!F(Jsisusb_open$B!G(J: drivers/usb/misc/sisusbvga/sisusb.c:2444: warning: $B!F(Jsisusb$B!G(J is used uninitialized in t...

Hi Jesper, > > - dev_err(&sisusb->sisusb_dev->dev, "Failed to find interface

Hey, thanks ;-) There are 13 in all, I just felt lazy and simply used ^R from alpine in-reply-to the first mail one-after-another instead of scripting it ... -

Make ide_rate_filter() also respect PIO/SWDMA/MWDMA mode masks. While at it, make the udma_filter() method calls take precedence over using the mode masks. --- This version doesn't use explicit UltraDMA masks, so converting them to the ATA_UDMA* is left for another, global patch. This patch against the current Linus' tree and unfortunately I was able to only compile test it since that tree gives MODPOST warning and dies early on bootup. drivers/ide/ide-dma.c | 7 +++-- drivers/ide/ide-lib....

Hi, with current git i got this when "ifconfig eth1" down. eth1 had a mac address which looked really like an eth1394 ethernet although the module was not loaded. Something is really broken in 2.6.23-currentgit. I always g= et the sysfs rename issues which are discussed to be an udev issue. Then i see a eth1394 mac address on an interface which typically shouldn exist (udev should rename the wireless to eth1) and when issueing an ifconfig eth1 down i get a=20 BUG: scheduling while atomic: ifco...

Upgraded my kernel from 2.6.23-rc2 to 2.6.23-rc5. System hangs (caps lock and scroll lock leds are both flashing). It *randomly* happens but most of the time during after login to KDE. I have not investigated it yet because I have not tried doing it before. Also the system is really not responding so I can't do much.. Just hope it blue screen so I can send the error code easily :) Just CC me bec I'm not subscribed. Regards, _______________________________...

Oh, I thought I was the only one. I also had a single hang+flashing Caps & Scroll Lock with -rc5, but haven't had one since. I had VMWare Player modules loaded at the time though, and I recently rebuilt them with the any-any-patch-113 (earlier versions would not build with very recent kernels). -rc4-git2 and -git3 never hung even with VMWare modules loaded. So I disabled the autoload of VMWare stuff. The problem has not reproduced so far. My system is a Dell D610, running updated Fe...

First of all, try this patch : --- a/net/ipv4/tcp_input.c +++ b/net/ipv4/tcp_input.c @@ -560,7 +560,7 @@ static u32 tcp_rto_min(struct sock *sk)         struct dst_entry *dst = __sk_dst_get(sk);         u32 rto_min = TCP_RTO_MIN;   -       if (dst_metric_locked(dst, RTAX_RTO_MIN)) +       if (dst && dst_metric_locked(dst, RTAX_RTO_MIN))                 rto_min = dst->metrics[RTAX_RTO_MIN-1];         return rto_min;  } If t...