All of lore.kernel.org
 help / color / mirror / Atom feed
* (no subject)
From: Durgaprasada Kalluraya @ 2002-12-19  7:33 UTC (permalink / raw)
  To: netfilter



Hi,

I have configured our firewall using IPtables. The configuration of the 
firewall is as follows...
Firewall host has 3 interfaces one for DMZ, one for LAN and one for external 
world(internet). All of our servers have a
static IP address. Our FTP server is wu-ftpd

Now there is no problem in accessing our DNS, WEB, SMTP and IMAP servers 
from outside. But the FTP server is
showing some strange problem. When our client tries to do a 'ls' in FTP 
session it is shows the following error message.

ftp> ls
200 PORT command successful.
425 Can't build data connection: Connection timed out.
ftp> bye

But if I try the same thing from outside using a dialup connection all works 
fine for me!!!!

when some one tries do a 'ls' from internal LAN on our FTP server then the 
following message is displayed.
ftp> ls
500 Illegal PORT Command
425 Can't build data connection: Connection timed out.
ftp>

Our rules related to FTP server are...

$IPTABLES -A FORWARD -i $LAN_IFACE -j ACCEPT
$IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT

$IPTABLES -A OUTPUT -p ALL -s $LO_IP -j ACCEPT
$IPTABLES -A OUTPUT -p ALL -s $LAN_IP -j ACCEPT
$IPTABLES -A OUTPUT -p ALL -s $INET_IP -j ACCEPT
$IPTABLES -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT


$IPTABLES -A FORWARD -i $INET_IFACE -o $DMZ_IFACE -m state --state 
ESTABLISHED,RELATED -j
ACCEPT
$IPTABLES -A FORWARD -p TCP -i $INET_IFACE -o $DMZ_IFACE -d $DMZ_FTP_IP 
--dport ftp -j allowed
$IPTABLES -A FORWARD -p TCP -i $INET_IFACE -o $DMZ_IFACE -d $DMZ_FTP_IP 
--dport ftp-data -j
allowed
$IPTABLES -t nat -A PREROUTING -p TCP -i $INET_IFACE -d $FTP_IP --dport ftp 
-j DNAT --to-destination
$DMZ_FTP_IP
$IPTABLES -t nat -A PREROUTING -p TCP -i $INET_IFACE -d $FTP_IP --dport 
ftp-data -j DNAT
--to-destination $DMZ_FTP_IP
$IPTABLES -t nat -A POSTROUTING -p TCP -s $LAN_IP_RANGE -j SNAT --to-source 
$DMZ_NAT

where
DMZ_FTP_IP is IP address of ftp server in DMZ
DMZ_IP is global IP address of ftp server.
INET_IFACE is Internet interface on firewall
DMZ_IFACE is DMZ interface on firewall.
LAN_IP_RANGE is Lan ip range.

Can anyone help me?

Thanks and Regards
Durgaprasada

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963



^ permalink raw reply

* Re: Printer error
From: Bill Pleasants @ 2002-12-19  7:33 UTC (permalink / raw)
  To: Ray Olszewski, linux-newbie

Ray Olszewski wrote:

> You did not provide some of the information I asked for (namely, the
> contents of /etc/resolv.conf), but from what you did provide, the
> likely source of the lprm problem is an inconsistency between your lpr
> setup and /etc/hosts . As you report below, your /etc/hosts file only
> identifies the machine as localhost.localdomain and not also as just
> localhost. Consequently, the resolver cannot associate localhost with
> your machine, as is illustrated by the ping failure you also report.

I failed to mention there is no resolv.conf file.

>
> Probably you can fix the lprm problem by editing the entry (yeah, I
> know it says "Do not remove", but this is editing, not removing) so it
> reads:
>
>         127.0.0.1    localhost.localdomain localhost
>
> Do that and see if lprm now works. If not, tell us what the problem
> now loks like.

    "[bill@localhost bill]$ lprm
    Printer 'Print@localhost' - cannot open connection - No such file or
directory
    Make sure the remote host supports the LPD protocol
    and accepts connections from this host and from non-privileged
(>1023) ports"

>
> As to the underlying problem ... by "Additional attempts to print", do
> you mean trying to print different files? Preferably something nice
> and easy, like a short text file (/etc/hosts itself will do for a
> test)? Does "lpq" show anything significant? If you power-cycle the
> printer, does it now start to print? DId the printer successfully
> print other files prior to failing with the final page of the MapQuest
> one?

After the change in the hosts file, I tried printing the hosts file from
gedit, another file from Open Office and your email from Mozilla.  (I
did not reboot.)

    "[bill@localhost bill]$ lpq
    Printer 'Print@localhost' - cannot open connection - No such file or
directory
    Make sure the remote host supports the LPD protocol
    and accepts connections from this host and from non-privileged
(>1023) ports"

Power cycling the printer did not print.  There is no error light
showing.  I don't remember if more than 2 pages printed.  It was a while
ago.  While I was logged on as root, I also changed the boot run level
from 3 to 5.

And then .. the Network Device Control failed to function so I rebooted.
And then .... the printer started and printed the 2 MapQuest pages (from
10/15 I see) and stopped with the "toner out" light flashing.  I pulled
the parallel plug, cycled the power, got the "ready" light, plugged the
parallel back and got the error light again.  clicking to print this
message did not change the printer.
And then ...... The NDC failed again so I changed the hosts file back,
rebooted and still no go.  So I copied this message to a floppy to take
to my MS computer to send.  So that's what the problem looks like.

>
> At 10:44 PM 12/17/02 -0500, Bill Pleasants wrote:
> [...]
>
>>> More immediately, how does your system do name-to-address
>>> resolution? Does it rely on /etc/hosts? If so, what are the contents
>>> of that file? Or does it use a nameserver? If so, is it accessable?
>>> And what are the contents of the /etc/resolv.conf file?
>>
>>
>> I have some notion of what name-to-address resolution is for the
>> internet but not what it is for the Linux OS.  /etc/hosts contains:
>>   "# Do not remove the following line, or various programs
>>   # that require network functionality will fail.
>>   127.0.0.1    localhost.localdomain
>>
>>>
>>> Does the message really say "local host" rather than "localhost"?
>>> What result do you get if (from the command line) you try "ping
>>> localhost"?
>>
>>
>> This is cut and paste:
>>    "[bill@localhost bill]$ lprm
>>    Get_local_host: 'localhost' IP address not available!"
>>
>>    "[bill@localhost bill]$ ping localhost
>>    ping: unknown host localhost"
>
> [...]
>
>>> Finally, as to your immediate problem ... if the third page of a
>>> epecific document continues to fail to print, while other docs print
>>> fine (do they? you haven't said), i'd suspect something odd about
>>> the specific document. Generically, you need to investigate how
>>> general the printing problem is before we can tackle it systematically.
>>
>>
>> I did not retain the file I first tried to print.  Additional
>> attempts to print have produced no response from the printer.  Thank
>> you for your offer to help.
>
> [...]
> --
> -------------------------------------------"Never tell me the
> odds!"--------
> Ray Olszewski                    -- Han Solo
> Palo Alto, California, USA              ray@comarre.com
>
-------------------------------------------------------------------------------

>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-newbie" 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.linux-learn.org/faqs
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

^ permalink raw reply

* LID state
From: Zdeněk OGAR Skalák @ 2002-12-19  7:29 UTC (permalink / raw)
  Cc: Andrew Grover, ACPI mailing list
In-Reply-To: <20021218221142.GA321@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hi,

	should you try this patch? It's simple (& maybe stupid), but it adds 
/proc/acpi/button/lid/*/state, which is the actual state of the lid. So you no
longer have to count events for lid :-) When the event lid happens, just ask the
state ....

	It's done by acpi_evaluate_integer( "_LID" ). 

	This patch is for acpi-20021205 for 2.4.20. It should be applied in
drivers/acpi dir.
It modifies only acpi_drivers.h & button.c. 

	Don't know, if it is linux-like coded, so somebody should take a look at.

	By
		Zdenek OGAR Skalak

-- 
Ing. Zdeněk OGAR Skalák
Monet+ a.s.
Zámecká 365
763 14 Zlín - Štípa, CZ
Tel: +420 / 577 110 411,  Fax: +420 / 577 914 557

[-- Attachment #2: acpi.diff --]
[-- Type: text/plain, Size: 2140 bytes --]

diff -r -c original/acpi_drivers.h new/acpi_drivers.h
*** original/acpi_drivers.h	Mon Dec  9 15:01:10 2002
--- new/acpi_drivers.h	Wed Dec 18 14:12:46 2002
***************
*** 86,91 ****
--- 86,92 ----
  #define ACPI_BUTTON_DRIVER_NAME		"ACPI Button Driver"
  #define ACPI_BUTTON_CLASS		"button"
  #define ACPI_BUTTON_FILE_INFO		"info"
+ #define ACPI_BUTTON_FILE_STATE		"state"
  #define ACPI_BUTTON_TYPE_UNKNOWN	0x00
  #define ACPI_BUTTON_NOTIFY_STATUS	0x80
  
diff -r -c original/button.c new/button.c
*** original/button.c	Mon Dec  9 11:13:45 2002
--- new/button.c	Thu Dec 19 08:17:35 2002
***************
*** 102,107 ****
--- 102,145 ----
  	return_VALUE(len);
  }
  
+ static int
+ acpi_button_lid_read_state(
+ 	char			*page,
+ 	char			**start,
+ 	off_t			off,
+ 	int 			count,
+ 	int 			*eof,
+ 	void			*data)
+ {
+ 	struct acpi_button	*button = (struct acpi_button *) data;
+ 	char			*p = page;
+ 	int			len = 0;
+ 	acpi_status		status=AE_OK;
+ 	unsigned long		state;
+ 
+ 	ACPI_FUNCTION_TRACE("acpi_button_lid_read_state");
+ 
+ 	if (!button || !button->device)
+ 		goto end;
+ 
+ 	status=acpi_evaluate_integer(button->handle,"_LID",NULL,&state);
+ 	if (ACPI_FAILURE(status)){
+ 	    p += sprintf(p, "state:      unsupported\n");
+ 	}
+ 	else{
+ 	    p += sprintf(p, "state:      %lu\n",state); 
+ 	}
+ 
+ end:
+ 	len = (p - page);
+ 	if (len <= off+count) *eof = 1;
+ 	*start = page + off;
+ 	len -= off;
+ 	if (len>count) len = count;
+ 	if (len<0) len = 0;
+ 
+ 	return_VALUE(len);
+ }
  
  static int
  acpi_button_add_fs (
***************
*** 148,153 ****
--- 186,205 ----
  	else {
  		entry->read_proc = acpi_button_read_info;
  		entry->data = acpi_driver_data(device);
+ 	}
+ 	
+ 	if (button->type==ACPI_BUTTON_TYPE_LID){
+ 	    /* 'state' [R] */
+ 	    entry = create_proc_entry(ACPI_BUTTON_FILE_STATE,
+ 			S_IRUGO, acpi_device_dir(device));
+ 	    if (!entry)
+ 		ACPI_DEBUG_PRINT((ACPI_DB_ERROR,
+ 			  "Unable to create '%s' fs entry\n",
+ 			   ACPI_BUTTON_FILE_STATE));
+ 	    else {
+ 		entry->read_proc = acpi_button_lid_read_state;
+ 		entry->data = acpi_driver_data(device);
+ 	    }
  	}
  
  	return_VALUE(0);

^ permalink raw reply

* Saving logs when system is started
From: plachninka @ 2002-12-19  7:37 UTC (permalink / raw)
  To: linux-kernel

Hi
Simple question: is any possibility to save system logs on floppy or
anywhere when system is started from ramdisk?
I still have a problem with scsi_hostadapter module and i would like to see
startup logs


regards

Mariusz Bozewicz


^ permalink raw reply

* Re: is dosemu-1.1.4.0.map needed?
From: Bart Oldeman @ 2002-12-19  7:21 UTC (permalink / raw)
  To: Grigory Batalov; +Cc: linux-msdos
In-Reply-To: <20021219100711.7c79bc01.grisxa@mail.ru>

On Thu, 19 Dec 2002, Grigory Batalov wrote:

> Why is that dosemu-1.1.4.0.map in /usr/share/dosemu ?
> Is it needed for something?

dosdebug looks for it.

Bart


^ permalink raw reply

* is dosemu-1.1.4.0.map needed?
From: Grigory Batalov @ 2002-12-19  7:07 UTC (permalink / raw)
  To: linux-msdos

Why is that dosemu-1.1.4.0.map in /usr/share/dosemu ?
Is it needed for something?

-- 
Grigory Batalov.

^ permalink raw reply

* Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
From: Timothy D. Witham @ 2002-12-19  6:08 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: linux-kernel
In-Reply-To: <747650000.1040281526@titus>

  Sorry, they changed it last week and my fingers still
have the old firmware. 

  www.osdl.org/cgi-bin/plm

TIm

On Wed, 2002-12-18 at 23:05, Martin J. Bligh wrote:
> > Related thought:
> >
> >   One of the things that we are trying to do is to automate
> > patch testing.
> >
> >   The PLM (www.osdl.org/plm) takes every patch that it gets
> > and does a quick "Does it compile test".  Right now there
> > are only 4 kernel configuration files that we try but we are
> > going to be adding more.  We could expand this to 100's
> > if needed as it would just be a matter of adding additional
> > hardware to make the compiles go faster in parallel.
> 
> URL doesn't seem to work. But would be cool if you had one SMP
> config, one UP with IO/APIC, and one without IO/APIC. I seem
> to break the middle one whenever I write a patch ;-(
> 
> M.
> 
> -
> 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/
-- 
Timothy D. Witham - Lab Director - wookie@osdlab.org
Open Source Development Lab Inc - A non-profit corporation
15275 SW Koll Parkway - Suite H - Beaverton OR, 97006
(503)-626-2455 x11 (office)    (503)-702-2871     (cell)
(503)-626-2436     (fax)


^ permalink raw reply

* Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
From: Martin J. Bligh @ 2002-12-19  7:05 UTC (permalink / raw)
  To: Timothy D. Witham; +Cc: linux-kernel
In-Reply-To: <1040276082.1476.30.camel@localhost.localdomain>

> Related thought:
>
>   One of the things that we are trying to do is to automate
> patch testing.
>
>   The PLM (www.osdl.org/plm) takes every patch that it gets
> and does a quick "Does it compile test".  Right now there
> are only 4 kernel configuration files that we try but we are
> going to be adding more.  We could expand this to 100's
> if needed as it would just be a matter of adding additional
> hardware to make the compiles go faster in parallel.

URL doesn't seem to work. But would be cool if you had one SMP
config, one UP with IO/APIC, and one without IO/APIC. I seem
to break the middle one whenever I write a patch ;-(

M.


^ permalink raw reply

* PPC: compile failure in 2.4.21-pre1 ide
From: Meelis Roos @ 2002-12-19  7:04 UTC (permalink / raw)
  To: linux-kernel

Perhaps this is known, but here it is anyway.

First, tens of these warnings:

In file included from /home/mroos/compile/linux-2.4/include/linux/modversions.h:127,
                 from /home/mroos/compile/linux-2.4/include/linux/module.h:21,
                 from printk.c:26:
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:37: warning: `__ver_eighty_ninty_three' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:9: warning: this is the location of the previous definition
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:39: warning: `__ver_ide_ata66_check' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:5: warning: this is the location of the previous definition
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:41: warning: `__ver_set_transfer' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:7: warning: this is the location of the previous definition
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:43: warning: `__ver_ide_auto_reduce_xfer' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:1: warning: this is the location of the previous definition
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:45: warning: `__ver_ide_driveid_update' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:3: warning: this is the location of the previous definition
/home/mroos/compile/linux-2.4/include/linux/modules/ide-iops.ver:47: warning: `__ver_ide_config_drive_speed' redefined
/home/mroos/compile/linux-2.4/include/linux/modules/ide-features.ver:11: warning: this is the location of the previous definition

Then this:

ide-iops.c: In function `ide_mm_insw':
ide-iops.c:113: warning: implicit declaration of function `__ide_mm_insw'
ide-iops.c: In function `ide_mm_insl':
ide-iops.c:123: warning: implicit declaration of function `__ide_mm_insl'
ide-iops.c: In function `ide_mm_outsw':
ide-iops.c:138: warning: implicit declaration of function `__ide_mm_outsw'
ide-iops.c: In function `ide_mm_outsl':
ide-iops.c:148: warning: implicit declaration of function `__ide_mm_outsl'

And finally this:

drivers/ide/idedriver.o(.text+0x21a8): In function `ide_mm_insw':
: undefined reference to `__ide_mm_insw'
drivers/ide/idedriver.o(.text+0x21a8): In function `ide_mm_insw':
: relocation truncated to fit: R_PPC_REL24 __ide_mm_insw
drivers/ide/idedriver.o(.text+0x21d4): In function `ide_mm_insl':
: undefined reference to `__ide_mm_insl'
drivers/ide/idedriver.o(.text+0x21d4): In function `ide_mm_insl':
: relocation truncated to fit: R_PPC_REL24 __ide_mm_insl
drivers/ide/idedriver.o(.text+0x220c): In function `ide_mm_outsw':
: undefined reference to `__ide_mm_outsw'
drivers/ide/idedriver.o(.text+0x220c): In function `ide_mm_outsw':
: relocation truncated to fit: R_PPC_REL24 __ide_mm_outsw
drivers/ide/idedriver.o(.text+0x2238): In function `ide_mm_outsl':
: undefined reference to `__ide_mm_outsl'
drivers/ide/idedriver.o(.text+0x2238): In function `ide_mm_outsl':
: relocation truncated to fit: R_PPC_REL24 __ide_mm_outsl

-- 
Meelis Roos (mroos@linux.ee)


^ permalink raw reply

* Re: modules oops in 2.5.52
From: Jeremy Fitzhardinge @ 2002-12-19  6:59 UTC (permalink / raw)
  To: Rusty Russell; +Cc: Linux Kernel List
In-Reply-To: <20021219063839.40F322C080@lists.samba.org>

On Wed, 2002-12-18 at 21:55, Rusty Russell wrote:
> Yes, it would be a problem.  But I don't think that's the problem
> here, and I don't think it can actually happen (it's a pretty insane
> idea).
> 
> BTW, I can't reproduce your problem, maybe because I can't unload
> parport_pc here:
> 
> Module parport cannot be unloaded due to unsafe usage in drivers/parport/init.c:234
> Module parport_pc cannot be unloaded due to unsafe usage in drivers/parport/parport_pc.c:1239

Well, I don't have any problem unloading it.  It doesn't show any
messages or other warnings.  It also doesn't crash any more, so I'm not
sure what's happening...

	J


^ permalink raw reply

* Re: Notification hooks
From: Joseph Fannin @ 2002-12-19  6:34 UTC (permalink / raw)
  To: Larry McVoy; +Cc: linux-kernel
In-Reply-To: <20021216092415.E432@work.bitmover.com>

[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]

On Mon, Dec 16, 2002 at 09:24:15AM -0800, Larry McVoy wrote:
> On Mon, Dec 16, 2002 at 05:19:25PM +0000, Dave Jones wrote:
> > On Mon, Dec 16, 2002 at 12:12:18PM -0500, Ben Collins wrote:
> >  > Linus, is there anyway I can request a hook so that anything that
> >  > changes drivers/ieee1394/ in your repo sends me an email with the diff
> >  > for just the files in that directory, and the changeset log? Is this
> >  > something that bkbits can do?
> >  > 
> >  > I'd bet lots of ppl would like similar hooks for their portions of the
> >  > source.
> > 
> > It'd be nice if the bkbits webpage had a "notify me" interface for files
> > in Linus' repository. This way not just the maintainers, but folks
> > interested in changes in that area can also see the changes.
> 
> Just for linux.bkbits.net or for the openlogging tree?  To remind people, 
> linux.bkbits.net has Linus/Marcelo trees but openlogging.org has the 
> union of all trees anywhere in the world.  And openlogging doesn't have
> contents, it just has comments.  

    Sorry to hijack this thread like this, but I can't find a better
forum for it.

    Several times I have browsed linux source trees at bkbits.net and
found a changeset I have wanted to have as a patch.  I can search for
the changeset, and read the commit messages, and even read the patch
on the screen, but there is no good way to download that patch as a
file (viewing the page source doesn't help because the patch has html
markup interspersed with it).

    The only way to get the patch is to either 'scrape' the screen
with copy and paste and try to fix the broken whitespace or to use bk
to clone the entire tree and extract the patch via bk export.  It's a
real pain, and for no good reason I can see.

    Would it be possible to add a link to the bkbits.net pages to an
un-marked up changeset patch?  It would be great to have this for
trees other than linux.bkbits.net too -- like Dave Jones'
agpgart.bkbits.net for example.

-- 
Joseph Fannin
jhf@rivenstone.net

"That's all I have to say about that." -- Forrest Gump.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply

* QOS
From: Paulo Andre @ 2002-12-19  6:48 UTC (permalink / raw)
  To: netfilter

Which is the better package to use for QOS??
HTB or CBQ..???

Paulo





^ permalink raw reply

* Re: [BUG] module-init-tools 0.9.3, rmmod modules with '-'
From: Vamsi Krishna S . @ 2002-12-19  7:11 UTC (permalink / raw)
  To: Kai Germaschewski; +Cc: Rusty Russell, Zwane Mwaikambo, lkml
In-Reply-To: <Pine.LNX.4.44.0212181144120.21707-100000@chaos.physics.uiowa.edu>

On Wed, Dec 18, 2002 at 11:47:26AM -0600, Kai Germaschewski wrote:
> On Wed, 18 Dec 2002, Rusty Russell wrote:
> 
> > In message <20021217114846.A30837@in.ibm.com> you write:
> > > On Tue, Dec 17, 2002 at 11:17:05AM +1100, Rusty Russell wrote:
> > > > 
> > > > BTW, this was done for (1) simplicity, (2) so KBUILD_MODNAME can be
> > > > used to construct identifiers, and (3) so parameters when the module
> > > > is built-in have a consistent name.
> > > > 
> > > Ok, I see it now, this magic happens in scripts/Makefile.lib. 
> > > My module has been built outside the kernel build system, that's
> > > why I saw this problem.
> > > 
> > > I guess avoiding '-' should do it, but is there a simple way to 
> > > correctly build (simple, test) modules outside the kernel tree now?
> > 
> > Has there ever been a simple way?
> 
> Well, you can do
> 
> cd my_module
> echo "obj-m := my_module.o" > Makefile
> vi my_module.c
> make -C <path/to/kernel/src> SUBDIRS=$PWD modules
> 
> That's not too bad (and basically works for 2.4 as well)
> 
That's way cool! Thank you.

-- 
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com

^ permalink raw reply

* RE: Linux 2.4.21-pre2
From: Mikael Starvik @ 2002-12-19  6:49 UTC (permalink / raw)
  To: 'Alan Cox', 'Christoph Hellwig'
  Cc: 'Marcelo Tosatti', 'starvik@axis.com',
	'lkml'

>It reverts the s/extern __inline__/static __inline__/g changes

We have replaced all static inline with extern inline to keep
the size of the image down when compiling with GCC 3.2 
(because the maximum size to inline has changed in 3.2 I think,
I can get a clarification from the gcc-cris guy if necessary).
Is this a non preferred way to do it?

>a junk file in arch/cris/drivers/bluetooth/bt.patch

Why is it junk? The bluetooth options should only be visible
if you have an OpenBT source tree available. The Makefile 
in arch/cris/drivers/bluetooth/ checks your tree and then
runs the patch. This was previously done with a perl 
script instead. In the long run we should probably switch
to the official Bluetooth stack in Linux (i.e. Bluez).

>although if Axis would glance over and fixup the ide bits
>that would be great as its not a platform I have access too

Yes, I will take a look at it

/Mikael

^ permalink raw reply

* Re: dosemu-1.1.4 and /var/lib/dosemu
From: Bart Oldeman @ 2002-12-19  6:42 UTC (permalink / raw)
  To: Stephen Lee; +Cc: dosemu
In-Reply-To: <1040277617.23284.1079.camel@ralph.plexio.private>

On 18 Dec 2002, Stephen Lee wrote:

> I've compiled dosemu-1.1.4 on a Redhat 7.2 (with all recent updates) box
> with the default settings and did a systemwide installation:
>
> ./install_systemwide -fd /usr/local/dosemu/dosemu-freedos-bin.tgz -i
> /usr/local/dosemu/

install_systemwide is deprecated; I think I'd better remove it next time,
or add a warning to it.

there are at least three ways to solve your problem:
a) mkdir /var/lib/dosemu
b) run "make install" instead of install_systemwide
c) change syshdimagedir in compiletime-settings from /var/lib/dosemu to
/usr/local/dosemu

Bart


^ permalink raw reply

* Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
From: Timothy D. Witham @ 2002-12-19  5:45 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Alan Cox, Linus Torvalds, Dave Jones, Horst von Brand,
	linux-kernel
In-Reply-To: <3E016A9F.52A4048@digeo.com>

On Wed, 2002-12-18 at 22:43, Andrew Morton wrote:
> "Timothy D. Witham" wrote:
> > 
> > Related thought:
> > 
> >   One of the things that we are trying to do is to automate
> > patch testing.
> > 
> >   The PLM (www.osdl.org/plm) takes every patch that it gets
> > and does a quick "Does it compile test".  Right now there
> > are only 4 kernel configuration files that we try but we are
> > going to be adding more.  We could expand this to 100's
> > if needed as it would just be a matter of adding additional
> > hardware to make the compiles go faster in parallel.
> 
> It would be valuable to be able to test that things compile
> cleanly on non-ia32 machines.  And boot, too.
> 
  The way the software is configured it is fairly easy to
add multiple servers (even different instruction sets) that
have the complies farmed out to them.

> That's probably a lot of ongoing work though.

  The largest portion of the work would be keeping
up with the breakages in the trees.

BTW I'm in Japan so my access times are going to be
a little strange.
-- 
Timothy D. Witham - Lab Director - wookie@osdlab.org
Open Source Development Lab Inc - A non-profit corporation
15275 SW Koll Parkway - Suite H - Beaverton OR, 97006
(503)-626-2455 x11 (office)    (503)-702-2871     (cell)
(503)-626-2436     (fax)


^ permalink raw reply

* Re: 2.4.19, don't "hdparm -I /dev/hde" if hde is on a Asus A7V133  Promise ctrlr, or...
From: Ross Vandegrift @ 2002-12-19  6:47 UTC (permalink / raw)
  To: D.A.M. Revok; +Cc: linux-kernel, rossb
In-Reply-To: <200212181635.58164.marvin@synapse.net>

On Wed, Dec 18, 2002 at 04:35:58PM -0500, D.A.M. Revok wrote:
> I figured out what it is, more...
> hdparm -X12 ( to set PIO instead of UDMA ) /does not/ fix it, so I dug 
> into BIOS and re-enabled the bios for that controller...

Ah, I can verify this has fixed the lockups for me too.  I previously
had the BIOS disabled cause it takes so long to boot, but recently
reenabled it.  smartctl can hapily operate on all drives now.

> Does my having the "bios" for that controller turned off create the 
> problem? ( I don't boot from those drives, so didn't see any reason to 
> have it...  )

I do now boot from my Promise controlled drives, and yes, I need the
BIOS.

-- 
Ross Vandegrift
ross@willow.seitz.com

A Pope has a Water Cannon.                               It is a Water Cannon.
He fires Holy-Water from it.                        It is a Holy-Water Cannon.
He Blesses it.                                 It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it.          It is a Wholly Holy Holy-Water Cannon.
He has it pierced.                It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official.       It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive.                                       He shoots them.

^ permalink raw reply

* Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
From: Andrew Morton @ 2002-12-19  6:43 UTC (permalink / raw)
  To: Timothy D. Witham
  Cc: Alan Cox, Linus Torvalds, Dave Jones, Horst von Brand,
	linux-kernel
In-Reply-To: <1040276082.1476.30.camel@localhost.localdomain>

"Timothy D. Witham" wrote:
> 
> Related thought:
> 
>   One of the things that we are trying to do is to automate
> patch testing.
> 
>   The PLM (www.osdl.org/plm) takes every patch that it gets
> and does a quick "Does it compile test".  Right now there
> are only 4 kernel configuration files that we try but we are
> going to be adding more.  We could expand this to 100's
> if needed as it would just be a matter of adding additional
> hardware to make the compiles go faster in parallel.

It would be valuable to be able to test that things compile
cleanly on non-ia32 machines.  And boot, too.

That's probably a lot of ongoing work though.

^ permalink raw reply

* Re: modules oops in 2.5.52
From: Rusty Russell @ 2002-12-19  5:55 UTC (permalink / raw)
  To: Jeremy Fitzhardinge; +Cc: Linux Kernel List
In-Reply-To: <1040271549.1317.12.camel@ixodes.goop.org>

In message <1040271549.1317.12.camel@ixodes.goop.org> you write:
> On Wed, 2002-12-18 at 18:11, Rusty Russell wrote:
> > In message <1040260444.1316.4.camel@ixodes.goop.org> you write:
> > > Hi,
> > > 
> > > I just had an oops in the modules code:
> > > 
> > > Dec 18 16:58:59 ixodes kernel: Unable to handle kernel paging request at 
virt
> > ual address f8980924
> > > Dec 18 16:58:59 ixodes kernel:  printing eip:
> > > Dec 18 16:58:59 ixodes kernel: f896756d
> > > Dec 18 16:58:59 ixodes kernel: *pde = 01bfc067
> > > Dec 18 16:58:59 ixodes kernel: *pte = 00000000
> > > Dec 18 16:58:59 ixodes kernel: Oops: 0000
> > > Dec 18 16:58:59 ixodes kernel: CPU:    0
> > > Dec 18 16:58:59 ixodes kernel: EIP:    0060:[<f896756d>]    Not tainted
> > > Dec 18 16:58:59 ixodes kernel: EFLAGS: 00010282
> > > Dec 18 16:58:59 ixodes kernel: EIP is at __exitfn+0xd/0x4c [parport_pc]
> > 
> > Actually, you had an oops in the parport_pc code, in
> > cleanup_module().  Now, *why* that oopsed, I don't know...
> 
> It looks like it might end up calling request_module() from within
> cleanup_module(). Is that going to be a problem?

Yes, it would be a problem.  But I don't think that's the problem
here, and I don't think it can actually happen (it's a pretty insane
idea).

BTW, I can't reproduce your problem, maybe because I can't unload
parport_pc here:

Module parport cannot be unloaded due to unsafe usage in drivers/parport/init.c:234
Module parport_pc cannot be unloaded due to unsafe usage in drivers/parport/parport_pc.c:1239

A little confused,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

^ permalink raw reply

* Re: Freezing.. (was Re: Intel P6 vs P7 system call performance)
From: Timothy D. Witham @ 2002-12-19  5:34 UTC (permalink / raw)
  To: Alan Cox
  Cc: Linus Torvalds, Dave Jones, Horst von Brand, linux-kernel,
	Andrew Morton
In-Reply-To: <200212181908.gBIJ82M03155@devserv.devel.redhat.com>

Related thought:

  One of the things that we are trying to do is to automate 
patch testing.

  The PLM (www.osdl.org/plm) takes every patch that it gets
and does a quick "Does it compile test".  Right now there
are only 4 kernel configuration files that we try but we are
going to be adding more.  We could expand this to 100's 
if needed as it would just be a matter of adding additional
hardware to make the compiles go faster in parallel.

  Here is the example of the output from a baseline kernel.

http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=986

  A patch would look the same.  The PASS reports are really
short and the FAIL reports just give you the configuration 
files and the tail of the output from the kernel make.

 We've talked to a couple of system vendors about expanding
this to take the configurations that have passed and running
them on their 10's of hardware platforms of interest and we 
would be very happy to expand this to a very large number of
configurations of all sorts.

Tim

On Wed, 2002-12-18 at 11:08, Alan Cox wrote:
> > And I think it could work for the kernel too, especially the stable
> > releases and for the process of getting there. I just don't really know
> > how to set it up well.
> 
> A start might be
> 
> 1.	Ack large patches you don't want with "Not for 2.6" instead
> 	of ignoring them. I'm bored of seeing the 18th resend of 
> 	this and that wildly bogus patch. 
> 
> 	Then people know the status
> 
> 2.	Apply patches only after they have been approved by the maintainer
> 	of that code area.
> 
> 	Where it is core code run it past Andrew, Al and other people
> 	with extremely good taste.
> 
> 3.	Anything which changes core stuff and needs new tools, setup
> 	etc please just say NO to for now. Modules was a mistake (hindsight
> 	I grant is a great thing), but its done. We don't want any more
> 
> 
> 4.	Violate 1-3 when appropriate as always, but preferably not to
> 	often and after consulting the good taste department 8)
> 
> Alan
> -
> 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/
-- 
Timothy D. Witham <wookie@osdl.org>
Open Sourcre Development Lab, Inc

^ permalink raw reply

* SUN SPARC (kernel?) issues
From: Jurzitza, Dieter @ 2002-12-19  6:29 UTC (permalink / raw)
  To: 'linux-kernel@vger.kernel.org'

Dear listmembers,
currently I am facing some difficulties on my SUN SPARC 
(ULTRA 60, Dualprocessor, SuSE Linux 7.3, 360 MHz) you might 
have an idea about:

- kernel is vanilla 2.4.20,

symptom:
Dec 12 11:16:42 oekalux08 kernel: Inspecting  /boot/System.map-2.4.20-SMP
Dec 12 11:16:42 oekalux08 kernel: Loaded 12988 symbols from
/boot/System.map-2.4.20-SMP.
Dec 12 11:16:42 oekalux08 kernel: Symbols match kernel version 2.4.20.
Dec 12 11:16:42 oekalux08 kernel: Error reading kernel symbols - Cannot
allocate memory 

The last line is the one I do not understand and that does 
not match the lines before. Does this impact the system stability?

Secondly I am facing difficulties with regard to network 
stability. After nfs-mounts I repeatedly had the entire 
system crash. This would look like:

(here I saw still a 2.4.19 kernel):

Nov 26 07:58:41 oekalux08 PAM-unix2[2935]: session started for user root,
service su 
Nov 26 07:58:57 oekalux08 kernel: Unable to handle kernel NULL pointer
dereference
Nov 26 07:58:57 oekalux08 kernel: tsk->{mm,active_mm}->context =
0000000000000775
Nov 26 07:58:57 oekalux08 kernel: tsk->{mm,active_mm}->pgd =
fffff8004c434000
Nov 26 07:58:57 oekalux08 kernel:               \|/ ____ \|/
Nov 26 07:58:57 oekalux08 kernel:               "@'/ .. \`@"
Nov 26 07:58:57 oekalux08 kernel:               /_| \__/ |_\
Nov 26 07:58:57 oekalux08 kernel:                  \__U_/
Nov 26 07:58:57 oekalux08 kernel: mount(2942): Oops
Nov 26 07:58:57 oekalux08 kernel: CPU[0]: local_irq_count[0] irqs_running[0]
Nov 26 07:58:57 oekalux08 kernel: TSTATE: 0000004411009601 
TPC: 00000000004330cc TNPC: 00000000004330d0 Y: 07000000 Tainted: P 
Nov 26 07:58:57 oekalux08 kernel: g0: 00000000000ab638 g1: 0000000000035ff0
g2: 0000000000000000 g3: fffffffffffffff8
Nov 26 07:58:57 oekalux08 kernel: g4: fffff80000000000 g5: 0000000000000000
g6: fffff8004d20c000 g7: 0000000000000000
Nov 26 07:58:57 oekalux08 kernel: o0: 000000000000fc00 o1: 0000000000000011
o2: 0000000000000000 o3: 0000000000000011
Nov 26 07:58:57 oekalux08 kernel: o4: 0000000000000080 o5: 0000000000000000
sp: fffff8004d20f501 ret_pc: 00000000004332d4
Nov 26 07:58:57 oekalux08 kernel: l0: fffff8004d20fdb0 l1: 0000000000000d80
l2: 0000000000010e3c l3: 000000007002a918
Nov 26 07:58:57 oekalux08 kernel: l4: 0000000070044b00 l5: 0000000000000000
l6: 00000000700003d0 l7: 000000007002a194
Nov 26 07:58:57 oekalux08 kernel: i0: 0000000000000000 i1: fffff8004d20feb0
i2: 0000000000000000 i3: 0000000000007fff
Nov 26 07:58:57 oekalux08 kernel: i4: 000000007002b230 i5: 0000000000000000
i6: fffff8004d20f601 i7: 0000000000433400
Nov 26 07:58:57 oekalux08 kernel: Caller[0000000000433400]
Nov 26 07:58:57 oekalux08 kernel: Caller[0000000000410934]
Nov 26 07:58:57 oekalux08 kernel: Caller[000000000001280c]
Nov 26 07:58:57 oekalux08 kernel: Instruction DUMP: 9de3bf00  
1100003f  a007a7af <d6162032> 901223ff  d4162036  80a2c008  d2162034
d424203c 
Nov 26 07:58:57 oekalux08 kernel: CPU[1]: local_irq_count[0] irqs_running[0]
Nov 26 07:58:57 oekalux08 kernel: TSTATE: 0000009900000a04 
TPC: 00000000700e9e74 TNPC: 00000000700e9e78 Y: 0078ebd0    Tainted: P 
Nov 26 07:58:57 oekalux08 kernel: g0: 0000000000000000 g1: 000000006c63feff
g2: 0000000070189c00 g3: fffffffffffff1f0
Nov 26 07:58:57 oekalux08 kernel: g4: 00000000006d6500 g5: 0000000000545a00
g6: 0000000000000000 g7: 0000006b65726e00
Nov 26 07:58:57 oekalux08 kernel: o0: 0000000000000e10 o1: 00000000fffffcf4
o2: 00000000fffffd3c o3: 00000000fffffd2c
Nov 26 07:58:57 oekalux08 kernel: o4: 00000000fffffd60 o5: 0000000000001c20
sp: 00000000efffec70 ret_pc: 00000000700e9e24
Nov 26 07:58:57 oekalux08 kernel: l0: 00004000 l1: 00025d30 l2: 00096820 l3:
0002a3ec l4: 00025400 l5: 00000000 l6: 
00000000 l7: 701878d4
Nov 26 07:58:57 oekalux08 kernel: i0: 3de31bb1 i1: 00000001 i2: fffffc00 i3:
efffed38 i4: 7018bea8 i5: 3de31bb1 i6: 
efffecd8 i7: 700e8d5c

Using 2.4.20 I haven't got this far. Simply:
Dec 12 09:59:11 oekalux08 kernel: nfs_read_super: get root inode failed
Dec 12 09:59:11 oekalux08 kernel: nfs warning: mount version older than
kernel
Dec 12 10:08:31 oekalux08 kernel: Unable to handle kernel paging request at
virtual address 0000000000010000

Any ideas? Many thanks for your support and help in advance, 
have a peaceful christmas eve and a happy new year,
take care



Dieter Jurzitza
 

-- 
________________________________________________

HARMAN BECKER AUTOMOTIVE SYSTEMS

Dr.-Ing. Dieter Jurzitza
Manager Hardware Systems
         ESI

Industriegebiet Ittersbach
Becker-Göring Str. 16
D-76307 Karlsbad / Germany

Phone: +49 (0)7248 71-1577
Fax:   +49 (0)7248 71-1216
eMail: JurzitzaD@Becker.de
Internet: http://www.becker.de


*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************


^ permalink raw reply

* Re: Intel sez: Synchronous Flash and XIP is the future -- thought s? -->NAND
From: Charles Manning @ 2002-12-19  6:41 UTC (permalink / raw)
  To: Paul Nash, Russ Dill, linux-mtd
In-Reply-To: <43CB1396676FD4119F03001083FD299401A1C91F@neptune.kirkland.local>

On Thu, 19 Dec 2002 02:13, Paul Nash wrote:
> So what are people out there using in their designs for NAND primarily? 
> Raw NAND?  NAND plus some bootable sector?  DiskOnChip?
>

NAND has been around for over ten years now, but the real uptake has only 
been very recent.

Until recently, most people have used DiskOnChip which is essentially just a 
raw NAND + an ASIC to do ECC + a very expensive price tag.

Probably most NAND in use is SmartMedia (numerically speaking) - using FAT. 
These are just raw nand on a carrier card. Just ask David Woodhouse what he 
thinks about that! THis is being superceded by XD card. 

Now that there are very reliable NAND file systems (JFFS2 and YAFFS) that run 
under Linux and other OSs, it is becoming increasingly palatable to use raw 
NAND parts soldered down, or use SmartMedia/XD if you want an expanadable 
system.

The new generation NAND parts expand to 16-bit data buses and have bootable 
code space. This makes it possible to build systems that are all NAND with no 
NOR in sight.

-- CHarles

^ permalink raw reply

* [patch] fix drivers/scsi/sd.c warnings
From: Andrew Morton @ 2002-12-19  6:04 UTC (permalink / raw)
  To: James Bottomley; +Cc: linux-scsi

Somebody forgot to test with CONFIG_LBD=n:

drivers/scsi/sd.c: In function `sd_init_command':
drivers/scsi/sd.c:304: warning: right shift count >= width of type
drivers/scsi/sd.c:305: warning: right shift count >= width of type
drivers/scsi/sd.c:306: warning: right shift count >= width of type
drivers/scsi/sd.c:307: warning: right shift count >= width of type
drivers/scsi/sd.c: In function `sd_read_capacity':
drivers/scsi/sd.c:1016: warning: left shift count >= width of type
drivers/scsi/sd.c:1017: warning: left shift count >= width of type
drivers/scsi/sd.c:1018: warning: left shift count >= width of type
drivers/scsi/sd.c:1019: warning: left shift count >= width of type



--- 25/drivers/scsi/sd.c~scsi-warnings	Wed Dec 18 22:01:40 2002
+++ 25-akpm/drivers/scsi/sd.c	Wed Dec 18 22:02:41 2002
@@ -174,7 +174,7 @@ static int sd_init_command(struct scsi_c
 {
 	unsigned int this_count, timeout;
 	struct gendisk *disk;
-	sector_t block;
+	u64 block;
 	struct scsi_device *sdp = SCpnt->device;
 
 	timeout = SD_TIMEOUT;
@@ -1013,10 +1013,10 @@ repeat:
 			(buffer[2] << 8) |
 			buffer[3]);			
 	} else {
-		sdkp->capacity = 1 + (((sector_t)buffer[0] << 56) |
-			((sector_t)buffer[1] << 48) |
-			((sector_t)buffer[2] << 40) |
-			((sector_t)buffer[3] << 32) |
+		sdkp->capacity = 1 + (((u64)buffer[0] << 56) |
+			((u64)buffer[1] << 48) |
+			((u64)buffer[2] << 40) |
+			((u64)buffer[3] << 32) |
 			((sector_t)buffer[4] << 24) |
 			((sector_t)buffer[5] << 16) |
 			((sector_t)buffer[6] << 8)  |

_

^ permalink raw reply

* dosemu-1.1.4 and /var/lib/dosemu
From: Stephen Lee @ 2002-12-19  6:00 UTC (permalink / raw)
  To: dosemu

I've compiled dosemu-1.1.4 on a Redhat 7.2 (with all recent updates) box
with the default settings and did a systemwide installation:

./install_systemwide -fd /usr/local/dosemu/dosemu-freedos-bin.tgz -i
/usr/local/dosemu/

I then created a user account (dosemu) and ran xdosemu and got:


   DOSEMU will run in its own X window.
   To terminate it you have three choices:
   - type <Ctrl>-C _here_ (not in the dosemu window)
   - type <Ctrl><Alt><PgDn> in the dosemu window
   - execute 'exitemu' at the DOS prompt

   Hint: if you want $HOME as DOS drive D:, then use the '-home' option

Running unpriviledged in low feature mode
Linux kernel 2.4.18; CPU speed is 2019809000 Hz
Dosemu-1.1.4.0 Running on CPU=586, FPU=1
no console
CONF aborted with: 
*** error: /var/lib/dosemu does not exist
    ... giving up.

I then linked /var/lib/dosemu to /usr/local/dosemu/bin/dosemu but a that
did not fix the error. 'dosemu -D+a -o debug' dumps the following:

CONF: config variable parser_version_3 set
CONF: config variable c_system set
CONF: Parsing builtin file.
CONF: config variable version_3_style_used set

Any suggestions on what else to report or adjustments to make? I don't
recall Dosemu 1.1.3.7 giving me this problem.

Thanks,
Stephen


^ permalink raw reply

* 2.5.52-mm2
From: Andrew Morton @ 2002-12-19  5:53 UTC (permalink / raw)
  To: lkml, linux-mm

url: http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.52/2.5.52-mm2/

. Big reorganisation of shared pagetable code.  It is a cleanup, and
  there should be no functional changes.  The diff is considerably
  easier to read now.

  In this patchset, shared pagetables are configurable again, and the
  default is "off".  This is because the intent is that pagetable sharing
  always be enabled (on ia32 at least).  But we want it to work when it
  is disabled too.  So in this -mm, pagetable sahring is disabled. 
  Henceforth it will be enabled.  Make sense?

. Added Bill Irwin's patches, get them some additional testing.

. The per-cpu kmalloc infrastructure.

. Another update of the patch management scripts is at

	http://www.zip.com.au/~akpm/linux/patches/patch-scripts-0.9/

  no great changes here.  Various fixes and tweaks.



Changes since 2.5.52-mm1:

+shpte-reorg.patch

 The shared pagetable patch reorganisation.

+shpte-reorg-fixes.patch

 Make it work with CONFIG_SHAREPTE=n

-lockless-current_kernel_time.patch

 Dropped for now, because it is ia32-only and it is time to get some
 non-ia32 testing done.

+block-allocator-doc.patch

 Some commentary.

+ext2-rename-vars.patch

 Make ext2_new_block() understandable

+remove-memshared.patch

 Remvoe /proc/meminfo:MemShared

+bin2bcd.patch

 Code consolidation/cleanup

+log_buf_size.patch

 Configurable printk buffer size.

+semtimedop-update.patch

 Wire up semtimedop() for 32-bit ia32 apps on ia64.

+nfs-kmap_atomic.patch

 Use kmap_atomic in NFS

+ext3-bh-dirty-race.patch

 Fix a rare BUG in ext3

+unalign-radix-tree-nodes.patch

 Space saving for radix_tree_nodes

+htlb-0.patch
+htlb-1.patch
+htlb-2.patch
+htlb-3.patch

 hugetlbpage updates

+kmalloc_percpu.patch

 per-cpu kmalloc infrastructure

+kmalloc_percpu-rtcache.patch
+kmalloc_percpu-mibs-1.patch
+kmalloc_percpu-mibs-2.patch
+kmalloc_percpu-mibs-3.patch

 Applications thereof

+wli-01_numaq_io.patch
+wli-02_do_sak.patch
+wli-03_proc_super.patch
+wli-04_cap_set_pg.patch
+wli-06_uml_get_task.patch
+wli-07_numaq_mem_map.patch
+wli-08_numaq_pgdat.patch
+wli-09_has_stopped_jobs.patch
+wli-10_inode_wait.patch
+wli-11_pgd_ctor.patch
+wli-12_pidhash_size.patch
+wli-13_rmap_nrpte.patch

 Bill's stuff.



All 78 patches:


linus.patch
  cset-1.883.3.60-to-1.900.txt.gz

kgdb.patch

sync_fs-deadlock-fix.patch
  sync_fs deadlock fix

shrink_list-dirty-page-race.patch
  fix a page dirtying race in vmscan.c

slab-poisoning.patch
  more informative slab poisoning

nommu-generic_file_readonly_mmap.patch
  Add generic_file_readonly_mmap() for nommu

dio-return-partial-result.patch

aio-direct-io-infrastructure.patch
  AIO support for raw/O_DIRECT

deferred-bio-dirtying.patch
  bio dirtying infrastructure

aio-direct-io.patch
  AIO support for raw/O_DIRECT

aio-dio-debug.patch

dio-reduce-context-switch-rate.patch
  Reduced wakeup rate in direct-io code

cputimes_stat.patch
  Retore per-cpu time accounting, with a config option

reduce-random-context-switch-rate.patch
  Reduce context switch rate due to the random driver

inlines-net.patch

rbtree-iosched.patch
  rbtree-based IO scheduler

deadsched-fix.patch
  deadline scheduler fix

quota-smp-locks.patch
  Subject: [PATCH] Quota SMP locks

shpte-ng.patch
  pagetable sharing for ia32

shpte-nonlinear.patch
  shpte: support nonlinear mappings and clean up clear_share_range()

shpte-reorg.patch

shpte-reorg-fixes.patch
  shared pagetable reorg fixes

shpte-always-on.patch
  Force CONFIG_SHAREPTE=y for ia32

ptrace-flush.patch
  Subject: [PATCH] ptrace on 2.5.44

buffer-debug.patch
  buffer.c debugging

misc.patch
  misc fixes

warn-null-wakeup.patch

pentium-II.patch
  Pentium-II support bits

rcu-stats.patch
  RCU statistics reporting

auto-unplug.patch
  self-unplugging request queues

less-unplugging.patch
  Remove most of the blk_run_queues() calls

ext3-fsync-speedup.patch
  Clean up ext3_sync_file()

remove-PF_NOWARN.patch
  Remove PF_NOWARN

scheduler-tunables.patch
  scheduler tunables

blocking-kswapd.patch
  Give kswapd writeback higher priority than pdflush

block-allocator-doc.patch
  ext2/3 commentary and cleanup

spread-find_group_other.patch
  ext2/3: better starting group for S_ISREG files

ext3-alloc-spread.patch
  ext3: smarter block allocation startup

ext2-alloc-spread.patch
  ext2: smarter block allocation startup

ext2-rename-vars.patch
  rename locals in ext2_new_block()

ext3-use-after-free.patch
  ext3 use-after-free bugfix

dio-always-kmalloc.patch
  direct-io: dynamically allocate struct dio

file-nr-doc-fix.patch
  Docs: fix explanation of file-nr

set_page_dirty_lock.patch
  fix set_page_dirty vs truncate&free races

remove-memshared.patch
  Remove /proc/meminfo:MemShared

bin2bcd.patch
  BIN_TO_BCD consolidation

log_buf_size.patch
  move LOG_BUF_SIZE to header/config

semtimedop-update.patch
  Enable semtimedop for ia64 32-bit emulation.

nfs-kmap_atomic.patch
  use kmap_atomic instaed of kmap in NFS client

ext3-bh-dirty-race.patch
  ext3: fix buffer dirtying

unalign-radix-tree-nodes.patch
  don't cacheline-align radix_tree_nodes

htlb-0.patch
  hugetlb bugfixes

htlb-1.patch
  hugetlb: report shared memory attachment counts

htlb-2.patch
  hugetlb: fix MAP_FIXED handling

htlb-3.patch
  hugetlbfs: set inode->i_size

kmalloc_percpu.patch
  kmalloc_percpu -- stripped down version

kmalloc_percpu-rtcache.patch
  Make rt_cache_stat use kmalloc_percpu

kmalloc_percpu-mibs-1.patch
  Change Networking mibs to use kmalloc_percpu -- 1/3

kmalloc_percpu-mibs-2.patch
  Change Networking mibs to use kmalloc_percpu -- 2/3

kmalloc_percpu-mibs-3.patch
  Change Networking mibs to use kmalloc_percpu -- 3/3

wli-01_numaq_io.patch
  (undescribed patch)

wli-02_do_sak.patch
  (undescribed patch)

wli-03_proc_super.patch
  (undescribed patch)

wli-04_cap_set_pg.patch
  (undescribed patch)

wli-06_uml_get_task.patch
  (undescribed patch)

wli-07_numaq_mem_map.patch
  (undescribed patch)

wli-08_numaq_pgdat.patch
  (undescribed patch)

wli-09_has_stopped_jobs.patch
  (undescribed patch)

wli-10_inode_wait.patch
  (undescribed patch)

wli-11_pgd_ctor.patch
  (undescribed patch)

wli-12_pidhash_size.patch
  (undescribed patch)

wli-13_rmap_nrpte.patch
  (undescribed patch)

dcache_rcu-2.patch
  dcache_rcu-2-2.5.51.patch

dcache_rcu-3.patch
  dcache_rcu-3-2.5.51.patch

page-walk-api.patch

page-walk-scsi.patch

page-walk-api-update.patch
  pagewalk API update

gup-check-valid.patch
  valid page test in get_user_pages()
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

^ permalink raw reply


This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.