Re: [PATCH] bulkmem.c - null ptr fixes for 2.4.4

Do we need to free the linked list in setup_regions? Would it be easier to try and preallocate the structures beforehand, and then fill them with the loop? Btw, we didn't find anything wrong with the first part of the patch. Praveen Srinivasan and Frederick Akalin Alan Cox wrote: >> kernel

Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

On Thu, May 24, 2001 at 09:34:04PM -0700, Aaron Lehmann wrote: > This message sparked a long thread on the debian-legal mailing list, > which is long since dead. I am personally very curious about whether > this has been resolved upstream. I consider it a very important issue, > which is why I

Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

On Fri, May 25, 2001 at 01:59:08AM -0400, Albert D. Cahalan wrote: > If a driver writes 0x63f30e44 (4 bytes) to the card, no problem? > Fine, how about 0x52e590a84fc8231e (8 bytes) then? You can see > where this is leading I hope: 200 kB is perfectly fine. Yes, I thought this way at first.

Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

> From: "Adam J. Richter" <[EMAIL PROTECTED]> > Date: Sun, 22 Apr 2001 12:53:48 -0700 > To: [EMAIL PROTECTED] > Subject: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h >[...] > I believe this infringinges the copyrights of the authors > of the code used in these drivers

Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

On Thu, May 24, 2001 at 10:00:15PM -0700, Matthew Jacob wrote: > > It is my opinion, such as it is, that a BSD copyright inside of a GPL package > does not, per se, weaken the GPL. The BSD copyright is, in fact, the more > permissive license. My reading of both licenses would have me believe

Re: Patch for PM in ymfpci (against 2.4.5-pre3)

> From: Jeff Garzik <[EMAIL PROTECTED]> > Looks ok, only a small nit: an include and 'pmdev' are left over from > the older PM implementation, and can be removed. Oops, here's a better one. -- Pete - PM support for

Re: Linux 2.4.4-ac17

Dear Mike , > > This one I tested with memleak. It wasn't a leak, it was dcache > growth. Under vm stress, it shrank down fine. > It will depends upon lot of thing :- 1.What is your size of ramfs , 2. Are you using any harddisk , 3. How many many files are you creating , 4. How frequently you

[CHECKER] Web interface to database

We've made the database of errors found as part of the MC project online. Some of the cool features are: - Over 3500 errors (not necessarily unique across versions) - Results for 12 checkers, across 18 Linux versions from 1.0 to 2.4.4 - Keyword search on the file, function, or cause of an error

Re: [PATCH] fsm.c - null ptr fixes for 2.4.4

We tried to minimize the amount of changes we made; your patch is far more extensive. As this is not our code, we felt it would be a bad idea to make changes to the underlying structure. Praveen Srinivasan and Frederick Akalin Kai Germaschewski wrote: > On Thu, 24 May 2001, Praveen

Re: Busy on BLKFLSBUF w/initrd

On Thu, 24 May 2001, Maciek Nowacki wrote: > Problem seems to be solved. Here is what I did, for anyone who is interested > in using a loopback file on a local disk as root: [snip recipe] > This method depends on the change_root() mechanism which I had assumed is > becoming obsolete. It works,

Re: Patch for PM in ymfpci (against 2.4.5-pre3)

Looks ok, only a small nit: an include and 'pmdev' are left over from the older PM implementation, and can be removed. -- Jeff Garzik | "Are you the police?" Building 1024| "No, ma'am. We're musicians." MandrakeSoft | - To unsubscribe from this list: send the line "unsubscribe

Re: 2.4 freezes on VIA KT133

Mark Hahn writes: > contrary to the implication here, I don't believe there is any *general* > problem with Linux/VIA/AMD stability. there are well-known issues > with specific items (VIA 686b, for instance), but VIA/AMD hardware > is quite suitable for servers. VIA hardware is not suitable

Re: PATCH: "Kernel Insider" (security optimization)

>Its a linux kernel modification, that allows to decide wich uid, pid or >file can open a tcp socket in listening state. - Putting access control on listen() [rather than socket()/bind()] seems like a really bad idea. In particular, in some cases one can bind to a port and receive messages

Copyright for drivers- two SCSI HBA drivers

> As a user of hardware which requires firmware like this, I have mixed > feelings, but feel strongly that requirements of the GPL clearly > override any measure of convenience. Are there any plans to remove the > binary-only firmware from the kernel, and/or eventually from the Linux > source

Re: [Re: How to add ntfs support]

Hi Anton So you are constructing a improved NTFS file driver. So when you have to check your written codes of file driver, will u recompile the whole kernel ? . That is what I am asking. I am in a way to build a new file system. I took NTFS as a sample one. I thought , I will first

Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h

This message sparked a long thread on the debian-legal mailing list, which is long since dead. I am personally very curious about whether this has been resolved upstream. I consider it a very important issue, which is why I asked for RMS' opinion. He said that what is being done is clearly not

Patch for PM in ymfpci (against 2.4.5-pre3)

I am sorry to be a poor maintainer, people were sending me patches to enable PM support for a long time. I took most of this from Paul Stewart, fixed a buglet, and factored common parts into a function. -- Pete * PM support for suspend/resume (without pm_register, proper PCI API); * Killed some

Re: Big-ish SCSI disks

On Fri, 25 May 2001, Greg Johnson wrote: > Hi kernel poeple, > > Can anyone out there say for certain that 76GB SCSI disks should > just work with kernel versions 2.2 and/or 2.4? We need to get some > big disk space and have heard reports of problems with disks > bigger than 30GB under linux. I

RE: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

> From: Andrew Morton [mailto:[EMAIL PROTECTED]] > > Andreas Dilger wrote: > > > > On a side note, does anyone know if the kernel does checking if the > > stack overflowed at any time? > > There's a little bit of code in show_task() which calculates > how close this task ever got to

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

Andreas Dilger wrote: > > Dawson Engler writes: > > Here are 37 errors where variables >= 1024 bytes are allocated on a > > function's stack. > > First of all, thanks very much for the work you are doing. It really > is useful, and a good way to catch those very rare error cases that > would

PATCH: "Kernel Insider" (security optimization)

Hello, i wrote a modification for kernels 2.4.x, actually it can be lodaded as a module and its not intrusive. I would love to get you opinions, critics, flames about it. Plase CC: me becouse im not in the list. thanx The whole package with a intructions is at

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

> > Ah, nice --- I keep meaning to tell the checker to demote its warning > > about NULL bugs or large stack vars in __init routines and/or routines > > that have the substring "init" in them ;-) > > Please, don't. These functions are often used from/as init_module(), > so they must handle the

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

On Thu, 24 May 2001, Dawson Engler wrote: > > check_nmi_watchdog() is __init and we know exactly when it's called. > > The interesting cases (SMP kernel, since for UP NR_CPUS==1) are: > > Ah, nice --- I keep meaning to tell the checker to demote its warning > about NULL bugs or large stack

Re: [CHECKER] error path memory leaks in 2.4.4 and 2.4.4-ac8

> Disagree > > > ahc = ahc_alloc(NULL, name); > > ahc_alloc frees name on error Wow. That would have been a really nasty "fix." Sorry about that -- the name "ahc_alloc" is a little counter-intuitive ;-) Thanks for the quick feedback. Dawson - To unsubscribe from this list: send the

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

> check_nmi_watchdog() is __init and we know exactly when it's called. > The interesting cases (SMP kernel, since for UP NR_CPUS==1) are: Ah, nice --- I keep meaning to tell the checker to demote its warning about NULL bugs or large stack vars in __init routines and/or routines that have the

[PATCH] memory leak in scsi_proc.c

Hi, If someone writes to a scsi adapter's /proc entry and that scsi adapter has not defined a proc_info() entry point, proc_scsi_write() will leak a page. Furthermore, no sense asking for a page if said proc_info() entry point does not exist. This patch fixes the above problem and patches

[PATCH] warning fixes for 2.4.5pre5

Here is a patch that fixes warnings when using gcc 3.0 snapshots to compile the kernel. Most of these warnings are for labels at the end of compound statements and extra tokens at the end of #endifs. The patch for linux/drivers/usb/pwc-uncompress.c adds includes to fix warnings where

Re: [CHECKER] error path memory leaks in 2.4.4 and 2.4.4-ac8

> These are all now either fixed or obsoleted in my tree, and I will send a > patch to Linus shortly. Thankyou. Good deal. Thanks for letting us know! > Do you find it useful to get a response such as this? Are you keeping track > of the bugs you find? (Or is it simply reassuring to confirm

Re: Ramdisk Initialization Problem

"H. Peter Anvin" <[EMAIL PROTECTED]> wrote : > > First of all, try the latest kernel if you are going to report a bug. > As far as i know , Regarding Ramdisk linux-2.4.4 and 2.4.1 are similar. , no body fixed this problem after 2.4.1 , If somebody please let me know . Anyhow i will try with

Re: Linux 2.4.4-ac17

Dear Alan , Have you noticed (or fixed ) :- 1. the Memory leakage in ramfs 2. initialization of Ramdisk. In you your new versions . I am adding some details about them , for your reference :- ### 1. the Memory leakage in ramfs (Subject of email was

SiS630 linking problems w/ 2.4.4-ac12

Hi, I`m trying to compile 2.4.4-ac12 with support for SiS accelerated framebuffer device in the kernel. It compiles fine but then I get the attached errors. I`m trying the ac12 cause the sis framebuffer from the stock kernel doesn`t even boot and there seem to be significant changes beetween

Re: Ramdisk Initialization Problem

Followup to: By author:"Jaswinder Singh" <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > I am using kernel 2.4.1 with compressed Ramdisk on Hitachi SH board , > with no battery. When i run kernel first time , it works fine , it >

Re: SyncPPP Generic PPP merge

Jeff Mcadams writes: > Indeed. And let me just throw out another thought. A clean abstraction > of the various portions of the PPP functionality is beneficial in other > ways. My personal pet project being to add L2TP support to the kernel > eventually. A good abstraction of the framing

Re: O_TRUNC problem on a full filesystem

Andreas Dilger wrote: > > Andrew writes: > > "Stephen C. Tweedie" wrote: > > > On Wed, May 23, 2001 at 07:55:48PM +1000, Andrew Morton wrote: > > > > When you truncated your file, the blocks remained preallocated > > > > on behalf of the file, and were hence considered "used". For > > > > some

Re: Two-machine cluster efficient approach(?) Comment? Thanks.

On Thu, May 24, 2001 at 06:32:10PM -0400, Chuck Wu wrote: > Two machines want to be accessed by the same IP address and > share workload. Can not change the router. Can only change > local linux system. Will the following approach work? Thanks. You should check out Linux Virtual Server; it does

Big-ish SCSI disks

Hi kernel poeple, Can anyone out there say for certain that 76GB SCSI disks should just work with kernel versions 2.2 and/or 2.4? We need to get some big disk space and have heard reports of problems with disks bigger than 30GB under linux. Thanks. Greg. --

Re: [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8

Junfeng Yang wrote: > > On Thu, 24 May 2001, Willem Riede wrote: > > > Dawson Engler wrote: > > > > > > Hi All, > > > > > > Enclosed are 103 potential errors where code gets a pointer from a > > > possibly-failing routine (kmalloc, etc) and dereferences it without > > > > > > [BUG] osst_do_scsi

Re: nfs mount by label not working.

[quoted lines by Philipp Matthias Hahn on May 24, 2001, at 09:31] >Do you realy mean what you wrote in the Subject line: > >Subject : Re: *nfs* mount by label not working. No, I mean ext2. It would appear that my mount command was a little old. A newer version of mount works. -- Dave Mielke

RE: Accelerated TCP/IP support from kernel

I'm curious.. do your cards support IPv6 and ECN ? Gerhard On Thu, 24 May 2001, Bharath Madhavan wrote: > Thanks a lot. That was useful info especially your last point > where you are saying that most of the area we can save is in > data processing and not in protocol processing. >

Linux 2.4.4-ac17

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/ Intermediate diffs are available from http://www.bzimage.org In terms of going through the code audit almost all the sound drivers still need fixing to lock against format changes during a

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

On Thu, May 24, 2001 at 05:08:40PM -0600, Andreas Dilger wrote: > I'm curious about this stack checker. Does it check for a single > stack allocation >= 1024 bytes, or does it also check for several > individual, smaller allocations which total >= 1024 bytes inside > a single function? That

RE: Kernel 2.4.x TODO

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Was the TODO list at http://linux24.sourceforge.net just > meant to be useful before 2.4.0 was released? I believe that is the case. > It seems to me that it would still be useful for (amongst > other things) > potential kernel hackers

Re: 2.4 freezes on VIA KT133

> This report is probably not very helpful, but it may be useful for those who > planned to purchase AMD / VIA solution for a server. contrary to the implication here, I don't believe there is any *general* problem with Linux/VIA/AMD stability. there are well-known issues with specific items

Re: 2.4.4 kernel freeze

Jens Gecius <[EMAIL PROTECTED]> writes: > > > what do you mean by freeze? in theory, the fact that the irq > > I cannot ping the machine anymore, no Ooops, no kernel messages, the > > attached screen is freezed (which implies that no more interrupts > > are handled, right?) > > Excuse

Re: [CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

> > > Error ---> > > > p, p->RIOHosts, p->RIOPortp, rio_termios, rio_termios); > > > > Not a bug - you need to teach your code that printf has formats that print the > > value of a pointer not dereference it > > > > Take another look. p is potentially bogus here, meaning

Re: [CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

Alan Cox writes: > > [BUG] seems possible --- or is some precondition guarenteed? > > /u2/engler/mc/oses/linux/2.4.4-ac8/net/ipv6/udp.c:438:udpv6_recvmsg: >ERROR:FREE:453:438: WARN: Use-after-free of "skb"! set by 'kfree_skb':453 > > Looks right. Left for DaveM It's wrong, in the

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

Dawson Engler writes: > Here are 37 errors where variables >= 1024 bytes are allocated on a > function's stack. First of all, thanks very much for the work you are doing. It really is useful, and a good way to catch those very rare error cases that would not otherwise be fixed. I'm curious

Re: nfs mount by label not working.

On Wed, 23 May 2001, Dave Mielke wrote: > Using kernel 2.2.17-14 as supplied by RedHat, and using mount from > mount-2.9u-4, mounting by label using the -L option does not work. > > mount -L backup1 /a Do you realy mean what you wrote in the Subject line: Subject : Re: *nfs* mount by label

2.4 freezes on VIA KT133

Hi ! I've yet seen similar freeze reports here in the past, so I decided to post my one too. The said system is a server, Athlon 850, no overclocking, no overheating, 100 Mhz FSB, 512 MB brand RAM, Abit KT7A board with VIA KT133. The system is heavy loaded in daytime, but almost idle at night.

Re: [CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

> [BUG] [fixed in 2.4.4] > /u2/engler/mc/oses/linux/2.4.4-ac8/drivers/block/cciss.c:686:cciss_ioctl: >ERROR:FREE:682:686: WARN: Use-after-free of "c"! set by 'cmd_free':682 [type=SECURITY] > { > /* Copy the data out of the buffer we created */ >

Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

At 22:10 24/05/2001, Dawson Engler wrote: [snip] >- >[BUG] >/u2/engler/mc/oses/linux/2.4.4-ac8/fs/ntfs/super.c:352:ntfs_get_free_cluster_count: >ERROR:VAR:352:352: suspicious var 'bits' = 2048 bytes:352 [nbytes=2048] > >static int

Re: [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8

On Thu, 24 May 2001, Willem Riede wrote: > Dawson Engler wrote: > > > > Hi All, > > > > Enclosed are 103 potential errors where code gets a pointer from a > > possibly-failing routine (kmalloc, etc) and dereferences it without > > > > [BUG] osst_do_scsi will never return NULL if argument SRpnt

Two-machine cluster efficient approach(?) Comment? Thanks.

Two machines want to be accessed by the same IP address and share workload. Can not change the router. Can only change local linux system. Will the following approach work? Thanks. Solution: - 1. Reserve an unused IP as the to be publicized "Server IP", actually no machine takes it.

Re: Accelerated TCP/IP support from kernel

Bharath Madhavan writes: > I am looking into a scenario where we have a NIC which performs > all the TCP/IP processing and basically the core CPU offloads all data from > the socket level interface onwards to this NIC. Why would you ever want to do this? Point 1: Support for new TCP

Re: [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8

At 22:09 24/05/2001, Dawson Engler wrote: [snip] >- >[BUG] >/u2/engler/mc/oses/linux/2.4.4-ac8/fs/ntfs/support.c:244:ntfs_dupuni2map: >ERROR:NULL:243:244: Passing unknown ptr "buf"! as arg 0 to call "memcpy"! >set by 'kmalloc':244 [nbytes

Re: Dying disk and filesystem choice.

> IMHO we are not that deep into code freeze anymore. Freevxfs got added > in linux-2.4.5-pre*, so I think that a patch that adds a useful feature > like badblock support would be OK. FreeVxFS changes precisely nothing in the behaviour of any other fs - its like adding a new driver. Updating

Accelerated TCP/IP support from kernel

Hello all, I am looking into a scenario where we have a NIC which performs all the TCP/IP processing and basically the core CPU offloads all data from the socket level interface onwards to this NIC. Can Linux do this as of now. I saw some limited support like TCP/IP checksumming being

Re: [CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

On Thu, 24 May 2001, Dawson Engler wrote: > Hi All, > > Enclosed are 24 bugs where code uses memory that has been freed. The > good thing about these bugs is that they are easy to fix. (Note: About > 5 of these have had patches submitted, so this list is a bit out of > date.) Enclosed is a

Re: [CHECKER] null bugs in 2.4.4 and 2.4.4-ac8

Dawson Engler wrote: > > Hi All, > > Enclosed are 103 potential errors where code gets a pointer from a > possibly-failing routine (kmalloc, etc) and dereferences it without > > [BUG] osst_do_scsi will never return NULL if argument SRpnt isn't NULL. But they >copy SRpnt back by *aSRpnt,

[2.4.4ac15/16] problems with stat or link

Hallo all, I get the mentioned error as often as longer the system is running. E.g.: > ls kviewshell/.libs/libkmultipage.so The following is what strace say's: (The problem-zone can be found between two lines) 3795 execve("/usr/local/bin/ls", ["ls", "-l",

Re: [CHECKER] error path memory leaks in 2.4.4 and 2.4.4-ac8

[EMAIL PROTECTED] said: > 1 | drivers/mtd/mtdchar.c > 1 | fs/jffs/jffs_fm.c > 2 | fs/jffs/intrep.c > 1 | drivers/mtd/slram.c > 1 | drivers/mtd/ftl.c > 1 | drivers/mtd/mtdram.c These are all now either fixed or obsoleted in my tree,

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

Daniel Phillips wrote: > > On Tuesday 22 May 2001 22:10, Andreas Dilger wrote: > > Peter Braam writes: > > > File system journal recovery can corrupt a snapshot, because it > > > copies data that needs to be preserved in a snapshot. During > > > journal replay such data may be copied again, but

Re: Dying disk and filesystem choice.

Hans Reiser <[EMAIL PROTECTED]> writes: > > > No, reiserfs does have badblock support > > You just have to get it as a separate patch from us because it was written after > code freeze. > > Hans > It might be nice to have a link to that patch from the "download" page. I didn't see that

Re: 2.2.19+ide: corrupts ide tape output

Greetings, and thank you for this information! I've just confirmed this. Both of my ATAPI tapes don't work reliably with the Promise Ultra100, but do work with the on board ALI 15x3 chipsets. Both disks in this box appear to work with both sets of controllers. After considerable difficulty,

Re: Dying disk and filesystem choice.

Erik Mouw wrote: > > On Thu, May 24, 2001 at 09:53:45AM -0700, Hans Reiser wrote: > > No, reiserfs does have badblock support > > > > You just have to get it as a separate patch from us because it was > > written after code freeze. > > IMHO we are not that deep into code freeze anymore.

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

On Thu, 24 May 2001, Edgar Toernig wrote: > > What *won't* happen is, you won't get side effects from opening > > your serial ports (you'd have to open them without O_DIRECTORY > > to get that) so that seems like a little step forward. > > As already said: depending on O_DIRECTORY breaks

Re: [CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

On Thu, 24 May 2001, Dawson Engler wrote: > [BUG] [BAD] Returns a freed pointer -- very very bad. ... and easy to fix. > /u2/engler/mc/oses/linux/2.4.4/fs/proc/generic.c:438:proc_symlink: >ERROR:FREE:430:438: WARN: Use-after-free of "ent"! set by 'kfree':430 > ent->namelen = len; >

[CHECKER] user-pointer bugs in 2.4.4 and 2.4.4-ac8

Hi All, Enclosed are 10 probable security holes where code treats a pointer as a bad user pointer in one place (by passing it as an argument to a *_user or verify_area routine) but then dereferences it, or passes it to a routine that does dereference it somewhere else. We've reported many of

Re: Dual Athlon on 2.2.19 ?

On Thu, May 24, 2001, Prasanna P Subash <[EMAIL PROTECTED]> wrote: > Without the patch below the boot up would hang right after it detected the > ide devices. > > After applying the patch it booted all the way but the keyboard would hang. > > BTW I'm trying to port this patch back to the 2.2.18

Re: Oops on booting 2.4.4

Pete Zaitcev wrote: > > May 23 02:46:24 localhost kernel: Process kudzu (pid: 219, > > stackpage=c7845000) > > May 23 02:46:24 localhost kernel: Stack: c12607e0 0400 0400 > > c73aa000 c122a060 c122a05c c122a058 c88fbb20 > > May 23 02:46:24 localhost kernel:03f1 03f1

Ramdisk Initialization Problem

I am using kernel 2.4.1 with compressed Ramdisk on Hitachi SH board , with no battery. When i run kernel first time , it works fine , it uncompress Ramdisk and i get my shell prompt .But when i restart it second time (with out removing power cable ) kernel dies when uncompressing

Re: Dual Athlon on 2.2.19 ?

Without the patch below the boot up would hang right after it detected the ide devices. After applying the patch it booted all the way but the keyboard would hang. BTW I'm trying to port this patch back to the 2.2.18 TL-Kernel. Are there anymore changes I have to look at ? ---

[CHECKER] error path memory leaks in 2.4.4 and 2.4.4-ac8

Hi All, This checker warns when you do not free allocated memory on failure paths. The error messages with "type=SECURITY" were emitted when the error path was triggered by a failed copy_*_user or eqvuivalent --- bad people can easily use these to make the kernel lose memory. Summary

[CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8

Hi All, Here are 37 errors where variables >= 1024 bytes are allocated on a function's stack. Summary for 2.4.4ac8-specific errors = 9 2.4.4-specific errors = 0 Common errors = 28

[CHECKER] null bugs in 2.4.4 and 2.4.4-ac8

Hi All, Enclosed are 103 potential errors where code gets a pointer from a possibly-failing routine (kmalloc, etc) and dereferences it without checking. Many follow the simple pattern of alloc-memset: private = kmalloc(sizeof(*private),GFP_KERNEL); memset(private, 0,

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

On Tuesday 22 May 2001 22:10, Andreas Dilger wrote: > Peter Braam writes: > > File system journal recovery can corrupt a snapshot, because it > > copies data that needs to be preserved in a snapshot. During > > journal replay such data may be copied again, but the source can > > have new data

[CHECKER] use of floating point in 2.4.4 and 2.4.4-ac8

Hi All, These check the rule "DO NOT USE FLOATING POINT IN THE KERNEL" on the 2.4.4 and 2.4.4-ac8 releases. There were 10 errors in all: 2.4.4-specific errors = 8 Common errors = 2 --

[CHECKER] free bugs in 2.4.4 and 2.4.4-ac8

Hi All, Enclosed are 24 bugs where code uses memory that has been freed. The good thing about these bugs is that they are easy to fix. (Note: About 5 of these have had patches submitted, so this list is a bit out of date.) Summary 2.4.4ac8-specific errors = 4 2.4.4-specific

Re: Dying disk and filesystem choice.

J Sloan wrote: > > Excellent! > > Will this be in resierfs 4.0 then? > > cu > > jjs > > Hans Reiser schrieb: > > > No, reiserfs does have badblock support > > > > You just have to get it as a separate patch from us because it was written after > > code freeze. No, version 4 won't ship

Re: O_TRUNC problem on a full filesystem

Stephen writes: > On Thu, May 24, 2001 at 11:24:10AM -0600, Andreas Dilger wrote: > > How have you done the ext3 preallocation code? > > Preallocation is currently disabled in ext3. Eventually I'll probably > get it going by adding a journal prepare-commit callback to allow the > filesystem to

Re: Dying disk and filesystem choice.

On Thu, May 24, 2001 at 09:53:45AM -0700, Hans Reiser wrote: > No, reiserfs does have badblock support > > You just have to get it as a separate patch from us because it was > written after code freeze. IMHO we are not that deep into code freeze anymore. Freevxfs got added in

Re: Dual Athlon on 2.2.19 ?

On Thu, 24 May 2001, Johannes Erdfelt wrote: > Which patch of mine did you apply? Which motherboard are you doing your > testing with? The dual tyan presumably. Or are there others you are aware of. -Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: Selectively refusing TCP connections

On Thu, May 24, 2001 at 12:15:44PM -0700, David Ford wrote: > Is there an example somewhere of this? I don't have one handy, but basically you have to hack libpcap a bit to push the generated filters using SO_ATTACH_FILTER onto a socket. The format (LPF) understood by the kernel is a superset

Re: Dual Athlon on 2.2.19 ?

On Thu, May 24, 2001, Prasanna P Subash <[EMAIL PROTECTED]> wrote: > I have a dual athlon on the 760MP chipset. > 2.2.20pre1 and 2 dont work. I got it to work partly after applying Johannes > Erdfel's 760MP patch in io_apic.c. Even after applying the patch, there > are messages like 2.2.20pre1

Re: Dual Athlon on 2.2.19 ?

Alan, I have a dual athlon on the 760MP chipset. 2.2.20pre1 and 2 dont work. I got it to work partly after applying Johannes Erdfel's 760MP patch in io_apic.c. Even after applying the patch, there are messages like hdc: IRQ probe failed(0) hdd: IRQ probe failed(0) hde: IRQ probe failed(0) hdc:

SyncPPP Generic PPP merge

From: "Alan Cox" <[EMAIL PROTECTED]> > I had hoped for 2.4 to use generic ppp with it. That might be the more > productive way to attack the problem. Generic PPP requires the user mode pppd to handle the LCP and NCPs, while syncppp implements these in the kernel. Instead of using ifconfig to

Re: Selectively refusing TCP connections

Is there an example somewhere of this? David >You can push a BPF (LPF) filter expression onto a LISTEN socket that checks >every incoming packet using SO_ATTACH_FILTER. > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]devicearguments from lookup)

Malcolm Beattie writes: > Andreas Dilger writes: > > PS - I used to think shrinking a filesystem online was useful, but there > > are a huge amount of problems with this and very few real-life > > benefits, as long as you can at least do offline shrinking. With > > proper LVM

Re: how to crash 2.4.4 w/SBLive

May 24 10:58:05 prototype kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 May 24 10:58:05 prototype kernel: printing eip: May 24 10:58:05 prototype kernel: c01bcb40 May 24 10:58:05 prototype kernel: *pde = May 24 10:58:05 prototype kernel: Oops:

Re: Busy on BLKFLSBUF w/initrd

Problem seems to be solved. Here is what I did, for anyone who is interested in using a loopback file on a local disk as root: - create a romfs initrd with /linuxrc -> /bin/sh and an empty /initrd dir - boot, with root=/dev/rd/1 init=/bin/sh - when /linuxrc comes up, cat /dev/rd/0 > /dev/rd/1

Re: aic7xxx problem on -ac series

On Thu, May 24, 2001 at 11:15:25AM -0700, Josh Logan wrote: > > I have also seen this problem... I don't have any ideas. Is this a > module or compiled in? > Compiled in. It connects the boot disk. Maybe it's not an aic7xxx problem but a pci one, since 2.4.5-pre uses the same version of the

Linux 2.4.4-ac16

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/ Intermediate diffs are available from http://www.bzimage.org This merges some of the pending changes. In terms of going through the code audit almost all the sound drivers still need fixing

Re: [PATCH] drivers/net/others

On Thu, May 24, 2001 at 09:00:20AM -0700, Jonathan Lundell wrote: [...] > > Fine. But: > > At 3:02 AM +0200 2001-05-24, Andrzej Krzysztofowicz wrote: > >-printk(version); > >+#ifdef MODULE > >+printk("s", version); > > printed_version = 1; > >+#endif /* MODULE */ > > ...is playing

Re: O_TRUNC problem on a full filesystem

Hi, On Thu, May 24, 2001 at 11:24:10AM -0600, Andreas Dilger wrote: > How have you done the ext3 preallocation code? Preallocation is currently disabled in ext3. Eventually I'll probably get it going by adding a journal prepare-commit callback to allow the filesystem to flush preallocation

Re: SyncPPP IPCP/LCP loop problem and patch

> I did not realize that syncppp does not implement > all the RFC1661 states. That's simply broken :( > A proper state machine implementation would be nice. syncppp.c -predates- RFC1661 I believe. > On the other hand, it works in a minimal way > for most people and it's supposed to be folded >

Re: aic7xxx problem on -ac series

I have also seen this problem... I don't have any ideas. Is this a module or compiled in? Later, JOSH On Thu, 24 May 2001, Costas Tavernarakis wrote: > Hi all, > > I'm not subscribed to LKML, so please Cc: me with any replies. > >

Re: Linux 2.4.4-ac14

David Weinehall wrote: > > We don't provide the binutils or gcc with the kernel either. The 6502 > > is a rather well known processor. Try plonking "6502 assembler" in > > google and you'll have a lot of choice. > > Me likee, finally asm in the kernel I can grok. Someone else who has trouble

Re: patch to put IDE drives in sleep-mode after an halt

On Thu, May 24, 2001 at 03:16:44PM +, Petr Vandrovec wrote: > On 24 May 01 at 14:59, peter k. wrote: > > > > auto-parking), and since all drives are voice coil drives, then they > > > should auto-park. But i've had problems with some hard drives that were > > > spinned down (when Win was

Re: [PATCH] include/linux/coda.h

Ryan Cumming wrote: > When compiling the kernel under FreeBSD, __KERNEL__ is defined, but > __linux__ is not. I think this is an error on the part of the header file, > because on non-Linux build environments, which would otherwise compile the > Linux kernel correctly, do not have __linux__

Newbie question

Hello all, I'm doing a project in linux, and I'm changing the driver of sym53c8xx (a SCSI board) to support Target mode. To receive data, we need 2 interrupts. One is for initializing all of the structures needed, and the second to send the data to the SCSI layer. What happens is that

  1   2   3   4   >