Question:
Is there still an issue of OOM process killer to
pickup undesirable process, and/or
that the amount of free system be properly updated
after one such victim process is killed
and a new and/or pending memory request comes in from a different
process
BEFORE the second victim process is
On Fri, 25 May 2001, Linus Torvalds wrote:
> If somebody can show that the above is worth it and worth implementing (ie
> the Al Viro kind of "I have a real-life schenario where I'd like to use
> it"), and implements it (should be a fairly trivial exercise), then I'll
> happily accept new
On Fri, 25 May 2001, Adam J. Richter wrote:
> 1 : a group, body, or mass composed of many distinct parts
> or individuals
> 2 a : the collecting of units or parts into a mass or whole
> b : the condition of being so collected
>
> You have to argue that
On 25 May 2001, Eric W. Biederman wrote:
>
> For the small random read case we could use a
> mapping->a_ops->readpartialpage
No, if so I'd prefer to just change "readpage()" to take the same kinds of
arguments commit_page() does, namely the beginning and end of the read
area.
Filesystems
Rogier Wolff wrote:
> The "we'll turn it on in February" warning is worth NOTHING in this
> situation: February comes and goes. March comes and goes. Everybody
> who read the warning will think: Ok, so I must be fine.
>
> A warning of the form: "ECN will go on as soon as this message clears
>
On Friday, May 25, 2001 09:21:42 AM -0700 Hans Reiser <[EMAIL PROTECTED]>
wrote:
> No, our policy is strictly in sync with and reflective of that of the
> rest of the linux-kernel. Since the ac series has a different policy, we
> can be different in regards to the ac series.
Not really, our
Doug Ledford wrote:
>"Adam J. Richter" wrote:
>> On the question of whether this is nothing more than
>> aggregation,
>Yes, on that very question, I would argue it is a mere aggregation.
>> the firmware works intimately with the device driver to
>> produce a unitary result.
On Fri, May 25, 2001 at 03:22:44PM +0200, Nemosoft Unv. wrote:
> On 25-May-01 Erik Mouw wrote:
> > On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote:
> > The format conversion shouldn't be there in the first place. Format
> > conversion is policy, so it doesn't belong in kernel. Note
I'm trying to find the easiest way to to deidcate one CPU to responding
to a specific Interrupt request.
That CPU should only listen for that request while all other CPU should
ignore the interrupt.
Any suggestions? Do I have to muck with the IO_APIC or is there a
simpler way which I just
75GB 80GB 180GB all work fine...
your issues are:
location of kernel, below 8GB until you have the chance to turn on lba32
in your lilo.conf...
2GB filesize limit bites people who use large disks more often (well at
least in my app), use reiserfs.
joelja
On Fri, 25 May 2001, Greg Johnson
Also sprach Paul Mackerras
>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
At 8:45 AM -0700 2001-05-25, dean gaudet wrote:
>i think it really depends on how you use current -- here's an alternative
>usage which can fold the extra addition into the structure offset
>calculations, and moves the task struct to the top of the stack.
>
>not that this really solves anything,
> VIA hardware is not suitable for anything until we _know_ the
> truth about what is wrong. VIA is hiding something big.
I dont think thats true
> Creative Labs ought to toast VIA over blaming the sound card. :-)
Of course the card might be buggy too
The big problem with VIA is not that
> which is why I asked for RMS' opinion. He said that what is being done
> is clearly not "mere aggregation", and that such firmware should be
> moved out of the kernel (and even the tarball) to stop violating the
> GPL and make Linux be free software.
Given that the firmware is a seperate work
[1.] One line summary of the problem:
Sample rate wrong for USB microphone - distorted noisy sampling.
[2.] Full description of the problem/report:
The Andrea NC-7100 Microphone, which works great on the Mac & Win 98,
does not work under Linux. Samples are recorded at exactly twice the proper
> This patch has been tested and the code does compile.
>
> Rich
>
> diff -urN -X /linux/dontdiff linux/arch/i386/math-emu/fpu_trig.c
> rb/arch/i386/math-emu/fpu_trig.c
> --- linux/arch/i386/math-emu/fpu_trig.c Fri Apr 6 12:42:47 2001
> +++ rb/arch/i386/math-emu/fpu_trig.c Tue May 22
"Adam J. Richter" wrote:
> On the question of whether this is nothing more than
> aggregation,
Yes, on that very question, I would argue it is a mere aggregation.
> the firmware works intimately with the device driver to
> produce a unitary result.
Irrelevant. All drivers work with
On Fri, 25 May 2001 08:31:24 -0700 (PDT),
dean gaudet <[EMAIL PROTECTED]> wrote:
>another possibility for a debugging mode for the kernel would be to hack
>gcc to emit something like the following in the prologue of every function
>(after the frame is allocated):
IKD already does that, via the
On Fri, 25 May 2001, Andi Kleen wrote:
> On Fri, May 25, 2001 at 04:03:57PM +0200, Oliver Neukum wrote:
> > Is there a reason for the task structure to be at the bottom rather than the
> > top of these two pages ?
>
> This way you save one addition for every current access; which adds to
> quite
> statements and extra tokens at the end of #endifs. The patch for
> linux/drivers/usb/pwc-uncompress.c adds includes to fix warnings where
> kmalloc(), kfree(), and EXPORT_SYMBOL_NONVERS() implicity declared.
The pwc-uncompress stuff wants ignoring and the -ac fixes picking up that
also
On Fri, May 25, 2001 at 01:20:00AM -0400, Scott Murray wrote:
> On Thu, 24 May 2001, Maciek Nowacki wrote:
>
> > This method depends on the change_root() mechanism which I had assumed is
> > becoming obsolete. It works, and there is no need to mess with
> > /proc/sys/kernel/real_root_dev if the
> From: Erik Mouw [mailto:[EMAIL PROTECTED]]
>
> On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote:
> > On 25-May-01 Norbert Preining wrote:
> > > According to ac ChangeLog:
> > > o Rip format conversion out of the pwc driver (me)
> > > | It belongs in user space..
Pavel Machek <[EMAIL PROTECTED]> writes:
> Hi!
>
> > Is anyone having problems with ACPI causing console problems in kernel
> > 2.4.4 w/ Intel's patches? When watching my system boot over the
> > serial console, things work fine. When looking at my VAIO-FX140's
> > LCD, my console no longer
another possibility for a debugging mode for the kernel would be to hack
gcc to emit something like the following in the prologue of every function
(after the frame is allocated):
movl %esp,%edx
andl %edx,0x1fff
cmpl %edx,sizeof(struct task)+512
jbe stack_overflow
See http://www.firstfloor.org/~andi/softnet/
~Randy
---
> From: sebastien person [mailto:[EMAIL PROTECTED]]
>
> Is there any documents that explain how upgrade network
> driver from 2.2. to 2.4.? that gives details on changes ...
>
> Or maybe best
Hi, list
In ll_rw_block.c, before calling block device specific request function
( i mean do_hd_request, do_ftl_request, ... ) the io_request_lock is
locking, and all interrupts are disabling. I know, that request handler
routine have to be atomic, but when we read data from a flash device (
Alan Cox wrote:
>
>> return;
>>
>/u2/engler/mc/oses/linux/2.4.4-ac8/drivers/char/drm/gamma_dma.c:573:gamma_dma_send_buffers:
> ERROR:FREE:561:573: WARN: Use-after-free of "last_buf"! set by 'drm_free_buffer':561
>> DRM_DEBUG("%d running\n", current->pid);
>
>
> Left
"Stephen C. Tweedie" <[EMAIL PROTECTED]> writes:
> Hi,
>
> On Wed, May 23, 2001 at 01:01:56PM -0700, Linus Torvalds wrote:
>
> > On Wed, 23 May 2001, Stephen C. Tweedie wrote:
> > > > that the filesystems already do. And you can do it a lot _better_ than the
>
> > > > current
Hi
> --- linux/arch/i386/math-emu/fpu_trig.c Fri Apr 6 12:42:47 2001
> +++ rb/arch/i386/math-emu/fpu_trig.c Tue May 22 16:44:57 2001
> @@ -1543,6 +1543,7 @@
> EXCEPTION(EX_INTERNAL | 0x116);
> return;
> #endif /* PARANOID */
>+return;
> }
> }
>
On Thu, May 24 2001, Paul Gortmaker wrote:
> Hal Duston wrote:
>
> > http://www.sound.net/~hald/projects/ps2esdi/ps2esdi-2.4.4-patch4
> >
> > Hal Duston
> > [EMAIL PROTECTED]
>
> You PS/2 ESDI guys might want to set the max sectors for your
> driver - old default used to be 128, currently 255
Greg Johnson <[EMAIL PROTECTED]> [01/05/25 08:51]:
> Have you experienced any issues like this?
> Have you successfuly built a kernel that booted on these machines?
I'm also a user of the machine Scott mentioned. We're booting it off
of a smaller scsi disk, not the 76G disks.
The disks are
> A small overflow of the kernel stack overwrites the struct task at the
> bottom of the stack, recovery is dubious at best because we rely on
> data in struct task. A large overflow of the kernel stack either
> corrupts the storage below this task's stack, which could hit anything,
> or it gets
Whenever I try to boot with root on LVM (using initrd), I get an oops. The
oops happens right after (trying to) unmount old (initrd) root. It also
happens when I run it with root=/dev/sdb (which is a plain ext2fs with no
LVM involved, other than the lvmcreate_initrd-generated initrd).
I patched
The confirmed talks for this year's UK Unix User Group Linux Developers'
Conference in Manchester (Friday 29th June to Sunday 1st July) are now
listed at:
http://www.ukuug.org/events/linux2001/speakers.shtml
together with short biographies of the speakers (with some photos).
Topics covered
Hi all,
this micropatch adds missing __init for winchip_mcheck_init() function.
Best regards.
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
diff -ur -X /usr/dontdiff
Hello all,
We will most probably be looking into supporting Gig MACs and that
is
the reason why I was wondering if HW assist will help.
We are talking of Gigs of network data (dont ask me the application!)
I dont know about IPv6 support, we havent thought of that.
But the point is, We can
Greetings,
On 25-May-01 Erik Mouw wrote:
> On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote:
>> That´s what you get for ripping out the guts of a driver. Have a nice
>> day.
>
> The format conversion shouldn't be there in the first place. Format
> conversion is policy, so it
> > contrary to the implication here, I don't believe there is any *general*
> > problem with Linux/VIA/AMD stability. there are well-known issues
...
> VIA hardware is not suitable for anything until we _know_ the
> truth about what is wrong. VIA is hiding something big.
this is INCORRECT: we
On Thursday, May 24, 2001 11:16:58 PM +0100 Alan Cox
<[EMAIL PROTECTED]> wrote:
>> 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
On Fri, 25 May 2001, Jaswinder Singh wrote:
> Dear Mike ,
>
> Are you using harddisk ?
The OS resides on disk, yes. I suppose I could plunk a minimal
system into ramfs, pivot_root and umount disk, but I don't see
any way that could matter for a memory leak.
(hmm.. locking up tho. script
Hi,
just purchased a mainboard from MSI (694D Pro-IR 2.0, MS-6321 2.0) with an
on-board RAID-controller from Promise. Booting with a 2.4.4 kernel causes a
panic right after detection of the PDC20265.
I checked the source code in ide-pci.c and saw that there is a special
handling for this chip
Hi folks,
I want to register a new Hook in the netfilter (from kernel 2.4.4)
canvas for IP. The struct
used for register is :
struct nf_hook_ops
{
struct list_head list;
/* User fills in from here down. */
nf_hookfn *hook;
int pf;
int hooknum;
/*
Andi Kleen wrote:
>
> On Fri, May 25, 2001 at 07:52:02AM -0400, Brian Gerst wrote:
> > Actually, you will never get a stack fault exception, since with a flat
> > stack segment you can never get a limit violation. All you will do is
> > corrupt the data in task struct and cause an oops later on
On Fri, 25 May 2001, Erik Mouw wrote:
> On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> > Erm... May I point you to the sysdep/libm-ieee754/e_j0.c? There's a bunch
> > of constants of unknown origin. If you want to modify the implementation
> > you most certainly want more
On Fri, May 25, 2001 at 07:52:02AM -0400, Brian Gerst wrote:
> Actually, you will never get a stack fault exception, since with a flat
> stack segment you can never get a limit violation. All you will do is
> corrupt the data in task struct and cause an oops later on when the
> kernel tries to
Andi Kleen wrote:
>
> 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
>
Hi,
Is there any documents that explain how upgrade network driver from 2.2.
to 2.4.? that gives details on changes ...
Or maybe best way is to compare same driver in the twice kernel version ?
thanks
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Dear Satish,
you are getting this error because , you are not defining MODULE during
compilation of your module.
Please Refer to http://packetstorm.securify.com/groups/thc/LKM_HACKING.html
Best Regards,
Jaswinder.
- Original Message -
From: "SATHISH.J" <[EMAIL PROTECTED]>
To: <[EMAIL
> "erik" == Erik Mouw <[EMAIL PROTECTED]> writes:
erik> 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.
erik> IMHO we are not
On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> Erm... May I point you to the sysdep/libm-ieee754/e_j0.c? There's a bunch
> of constants of unknown origin. If you want to modify the implementation
> you most certainly want more than numeric values.
Nothing special IMHO. Look up
On Fri, May 25, 2001 at 12:44:30PM +0530, SATHISH.J wrote:
> I compiled the ramfilesystem under fs/ramfs and got the object file
> inode.o.
>
> 1.Should I do insmod to insert this module.
No, you should insmod ramfs.o.
> 2.After inserting this module how can I use "mkfs" to make this file
>
On Fri, May 25, 2001 at 10:48:12AM +0200, Nemosoft Unv. wrote:
> On 25-May-01 Norbert Preining wrote:
> > According to ac ChangeLog:
> > o Rip format conversion out of the pwc driver (me)
> > | It belongs in user space..
> >
> > This change is included in 2.4.5-pre6, but
> >
> Not to sound dense, but what part of the GPL prohibits a piece of GPL'd
> software from including non-GPL'd code? The GPL does explicitly state
> that you can't include it's software in proprietary code, but I don't
> recall seeing a provision that prohibits the other way around.
The same
> According to ac ChangeLog:
> o Rip format conversion out of the pwc driver (me)
> | It belongs in user space..
>
> This change is included in 2.4.5-pre6, but
> drivers/usb/pwc-uncompress.c
> still relies on this files:
Looks like I managed to send Linus a partial patch only.
Hi all,
Sorry for disturbing you with my doubt.
I tried to insert a module(my own object file called dssp.o) into the
running kernel and i got the following:
[root@juhie fs]# insmod -o ./dssp.o -f dssp
Using /lib/modules/2.2.14-12/fs/dssp.o
/lib/modules/2.2.14-12/fs/dssp.o: couldn't find the
On Thursday 24 May 2001 22:59, Edgar Toernig wrote:
> Daniel Phillips wrote:
> > > > Readdir fills in a directory type, so ls sees it as a directory
> > > > and does the right thing. On the other hand, we know we're on
> > > > a device filesystem so we will next open the name as a regular
> > >
On Friday 25 May 2001 00:00, Hans Reiser wrote:
> Daniel Phillips wrote:
> > I suppose I'm just reiterating the obvious, but we should
> > eventually have a generic filesystem transaction API at the VFS
> > level, once we have enough data points to know what the One True
> > API should be.
>
>
Here's a surprise. I think the problems with the keyspan
copyrights may have sprung from an administrative error. I notice that
the copyright notices in
linux-2.4.*/drivers/usb/serial/keyspan_usa{26,28,49}msg.h, which look
GPL compatible to me, look as if they were intended for
Dear Mike ,
Are you using harddisk ?
Jaswinder.
- Original Message -
From: "Mike Galbraith" <[EMAIL PROTECTED]>
To: "Jaswinder Singh" <[EMAIL PROTECTED]>
Cc: "Alan Cox" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, May 25, 2001 2:06 AM
Subject: Re: Linux 2.4.4-ac17
> On
On Fri, May 25, 2001 at 04:04:50AM -0400, Eric S. Raymond wrote:
> On further investigation I find that neither of these symbols is actually
> set in the ARM config file! This is kind of a mess. Is it going to be
> fixed in the next merge?
No. I don't have the fixes for it yet. (Phil -
Hi,
fixed patch poster earlier. PINE's default editor munged it up. Also changed
the 8 spaces indentation to a tab character.
Sorry about that.
> 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
Hi Andrzej,
Some hopefully useful/constructive feedback:
Andrzej Krzysztofowicz wrote:
>
> +static char version[]
> +#ifdef MODULE
> + __initdata
> +#else
> + __devinitdata
> +#endif
> + = KERN_INFO RTL8139_DRIVER_NAME "\n";
This doesn't look right. If defined(MODULE) then
Hal Duston wrote:
> http://www.sound.net/~hald/projects/ps2esdi/ps2esdi-2.4.4-patch4
>
> Hal Duston
> [EMAIL PROTECTED]
You PS/2 ESDI guys might want to set the max sectors for your
driver - old default used to be 128, currently 255 (which maybe
hardware can handle ok?) - the xd and hd drivers
I'm running stock 2.4.4 on five PCs with these features: ServerWorks
III HE, 2x 933MHz, 4GB RAM, dual-channel sym53c896 (FAST-40 WIDE) SCSI
controller. One PC has the new 181GB Seagate SCSI drive; another uses a
3ware RAID controller with 4x 40GB IDE (looks like a 160GB SCSI drive).
All is fine
Not to sound dense, but what part of the GPL prohibits a piece of GPL'd
software from including non-GPL'd code? The GPL does explicitly state
that you can't include it's software in proprietary code, but I don't
recall seeing a provision that prohibits the other way around.
It may not be in the
Hi,
On Fri, May 25, 2001 at 10:24:49AM +1000, Andrew Morton wrote:
> For example, when we miss the goal block we search forward
> up to 63 blocks for a *single* free block, and use that.
> Perhaps we shouldn't?
The reasoning here is that it's much cheaper to go to a single block
which is very
>> = Aaron Lehmann <[EMAIL PROTECTED]>.
> = Albert D. Cahalan <[EMAIL PROTECTED]>
>> I believe this infringinges the copyrights of the authors
>> of the code used in these drivers who released their code under GPL.
>> Alan Cox, has gone on a campaign claiming that this is "mere
On Thu, 24 May 2001, Jaswinder Singh wrote:
> 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 ,
unlimited.
> 2. Are you using any
[EMAIL PROTECTED] said:
> BTW the printk probably should be KERN_ERR, because this "warning" is
> fatal.
Surely it's only fatal if it's the root filesystem, and the panic() message
on being unable to mount the root filesystem already has a higher loglevel?
--
dwmw2
-
To unsubscribe from
Hi,
At 05:40 25/05/2001, Blesson Paul wrote:
>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
Greetings,
On 25-May-01 Norbert Preining wrote:
> Hi!
>
> According to ac ChangeLog:
> o Rip format conversion out of the pwc driver (me)
> | It belongs in user space..
>
> This change is included in 2.4.5-pre6, but
> drivers/usb/pwc-uncompress.c
> still relies on this
[EMAIL PROTECTED] said:
> I'm trying to run jffs on my ATA-flash disk (running ext2 could kill
> some flash cells too soon, right?) but it refuses:
CompactFlash does wear levelling internally.
> if (MAJOR(dev) != MTD_BLOCK_MAJOR) {
> printk(KERN_WARNING "JFFS: Trying
Hi!
> > IMVHO every developer involved in memory-management (and indeed, any
> > software development; the authors of ntpd comes in mind here) should
> > have a 386 with 4MB of RAM and some 16MB of swap. Nowadays I have the
> > luxury of a 486 with 8MB of RAM and 32MB of swap as a firewall, but
On Fri, 25 May 2001 10:27:53 +0200,
Andi Kleen <[EMAIL PROTECTED]> wrote:
>On Fri, May 25, 2001 at 06:25:57PM +1000, Keith Owens wrote:
>> Nothing in arch/i386/kernel/traps.c uses a task gate, they are all
>> interrupt, trap, system or call gates. I guarantee that kdb on ix86
>> and ia64 uses
Le Wed, 23 May 2001 16:58:15 +0200 (MET DST)
Andrzej Krzysztofowicz <[EMAIL PROTECTED]> a ecrit :
> "sebastien person wrote:"
> > Is it bad to do the following call ?
> >
> > mod_timer(, jiffies+(0.1*HZ));
>
> Yes, it is bad. Don't use floating point in the kernel if you don't
need.
So,
On Fri, May 25, 2001 at 06:25:57PM +1000, Keith Owens wrote:
> Nothing in arch/i386/kernel/traps.c uses a task gate, they are all
> interrupt, trap, system or call gates. I guarantee that kdb on ix86
> and ia64 uses the same kernel stack as the failing task, the starting
> point for the kdb
On Fri, 25 May 2001 10:20:15 +0200,
Andi Kleen <[EMAIL PROTECTED]> wrote:
>On Fri, May 25, 2001 at 04:53:47PM +1000, Keith Owens wrote:
>> The only way to avoid those problems is to move struct task out of the
>> kernel stack pages and to use a task gate for the stack fault and
>> double fault
I'm seeing the same thing on a vanillia 2.4.4 kernel.
It works on 2.2.18.
Christophe
On Thu, 24 May 2001 10:15:02 [EMAIL PROTECTED] wrote:
>
> [1.] fifo behaviour is broken in 2.4.4
>
> [2.] fifo are being flushed. Sending characters to a fifo, select(2)
> returns
> 'ready to read' on the
Hi!
> Is anyone having problems with ACPI causing console problems in kernel
> 2.4.4 w/ Intel's patches? When watching my system boot over the
> serial console, things work fine. When looking at my VAIO-FX140's
> LCD, my console no longer updates after ACPI starts initializing _INI methods.
Hi!!
> This project has been there for over one year, and I've got quite a few
> emails asking about it. Before it becomes more reliable, I think letting
> more people know about it is a good idea. Thanks to those who ever
> pushed me on it :-)
>
> I guess many of you have already known about
Hi!
> I will be using Linux as the OS for an embedded system.
> I was looking into 2.4.4 kernel code and saw the dcache implementation
> in VFS which is pretty neat and fast by itself.
>
> My question is, will I gain any considerable efficiency in file system
> access
> if I can move this
Hi!
I'm trying to run jffs on my ATA-flash disk (running ext2 could kill
some flash cells too soon, right?) but it refuses:
if (MAJOR(dev) != MTD_BLOCK_MAJOR) {
printk(KERN_WARNING "JFFS: Trying to mount a "
"non-mtd device.\n");
Hi!
BTW the printk probably should be KERN_ERR, because this "warning" is
fatal.
Pavel
inode-v23.c-if (MAJOR(dev) != MTD_BLOCK_MAJOR) {
inode-v23.c-printk(KERN_WARNING "JFFS: Trying to mount a "
inode-v23.c:
On Fri, May 25, 2001 at 04:53:47PM +1000, Keith Owens wrote:
> The only way to avoid those problems is to move struct task out of the
> kernel stack pages and to use a task gate for the stack fault and
> double fault handlers, instead of a trap gate (all ix86 specific).
> Those methods are
On Fri, May 25, 2001 at 03:20:20PM +1000, Keith Owens wrote:
> ftp://ftp.ocs.com.au/pub/kernel.stack.gz. ix86 specific, probably gcc
> specific and it only picks up code that you compile. The Stanford
> checker is much better.
I have no complete understanding of the stanford checker, but I was
On Wed, May 23, 2001 at 05:51:50PM +, Scott Anderson wrote:
> David Weinehall wrote:
> > IMVHO every developer involved in memory-management (and indeed, any
> > software development; the authors of ntpd comes in mind here) should
> > have a 386 with 4MB of RAM and some 16MB of swap. Nowadays
On Fri, 25 May 2001 08:11:07 +0100,
David Welch <[EMAIL PROTECTED]> wrote:
>Why not use a task gate for the double fault handler points to a
>per-processor TSS with a seperate stack. This would allow limited recovery
>from a kernel stack overlay.
It is far too late by then. struct task is at
Philip Blundell <[EMAIL PROTECTED]>:
> >CONFIG_ARCH_FTVPCI
> >CONFIG_ARCH_NEXUSPCI
>
> These symbols both refer to the same thing (the latter is an obsolete name).
> I guess appropriate text would be something like:
>
> Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
>
Hi all,
patch for lp486e.c network driver attached.
Changes: check_region() call removed, added missing __init and __exit.
Best regards.
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
diff -ur
On Fri, May 25, 2001 at 03:20:20PM +1000, Keith Owens wrote:
>
> >> On a side note, does anyone know if the kernel does checking if the
> >> stack overflowed at any time?
> >
> >You normally get a silent hang or worse a stack fault exception
> >(which linux/x86 without kdb cannot recover from)
On 25 May 2001, Andreas Jaeger wrote:
> We have comments in the code that state how j0 is build, and R0/S0
> come from some expansion:
> * Bessel function of the first and second kinds of order zero.
> * Method -- j0(x):
> *1. For tiny x, we use j0(x) = 1 - x^2/4 + x^4/64 - ...
> *
Aaron Lehmann <[EMAIL PROTECTED]> writes:
> On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> > Should we file bug reports against glibc?
>
> invsqrtpi= 5.64189583547756279280e-01
> Inverted square root of pi. Want to file a bug on Pi?
>
> tpi =
On Thu, 24 May 2001, Aaron Lehmann wrote:
> On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> > Should we file bug reports against glibc?
>
> invsqrtpi= 5.64189583547756279280e-01
> Inverted square root of pi. Want to file a bug on Pi?
Nope. Well-known constant.
> tpi
Hi all,
Please excuse me if my doubt is silly but do help me in answering this.
I compiled the ramfilesystem under fs/ramfs and got the object file
inode.o.
1.Should I do insmod to insert this module.
2.After inserting this module how can I use "mkfs" to make this file
system befor mounting
Hi!
According to ac ChangeLog:
o Rip format conversion out of the pwc driver (me)
| It belongs in user space..
This change is included in 2.4.5-pre6, but
drivers/usb/pwc-uncompress.c
still relies on this files:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.5.6-packet/include
On Fri, May 25, 2001 at 02:34:05AM -0400, Alexander Viro wrote:
> Should we file bug reports against glibc?
invsqrtpi= 5.64189583547756279280e-01
Inverted square root of pi. Want to file a bug on Pi?
tpi = 6.36619772367581382433e-01,
R0/S0 on [0, 2.00]
I'm not sure what R and S are, but
Keith Owens writes:
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> >At one time someone had a script to grep objdump -S vmlinux for the
> >stack allocations generated by gcc and check them.
>
> ftp://ftp.ocs.com.au/pub/kernel.stack.gz. ix86 specific, probably gcc
> specific and it only picks up code
On Thu, 24 May 2001, Aaron Lehmann wrote:
> explicit about defining source code:
> The source code for a work means the preferred form of the work for
> making modifications to it.
Erm... May I point you to the sysdep/libm-ieee754/e_j0.c? There's a bunch
of constants of unknown
Keith Owens <[EMAIL PROTECTED]>:
> I claim my erudition prize (do I get steak knives with that?).
Results doubtful. Consult Magic 8-Ball again :-).
I'm going to critique these individually pour encourager les autres.
> +Disable IA-64 Virtual Hash Page Table
> +CONFIG_DISABLE_VHPT
> + The
On Thu, May 24, 2001 at 11:26:20PM -0700, Matthew Jacob wrote:
> Sure- that's not BSD. You were speaking about all kinds of firmware, at least
> I thought you were. Must be too short on sleep.
Yes, I am. New-style BSD licenses are compatible with the GPL. As long
as a piece of firmware contains
101 - 200 of 401 matches
Mail list logo
