Jesse Pollard wrote:
> Ummm maybe. A SANS newsletter indicated that none of the current virus scanners
> even look at the other data streams (yet).
I attribute that to MS not showing data streams, er, I just call them forks, in
Explorer. If users were more aware of forks, and could manipulate
Guido Trentalancia schrieb:
>
> On Wed, 06 Sep 2000, you wrote:
> > Guido Trentalancia schrieb:
> >
> > Hello Guido,
> >
> > > >Hi !
> > > >This is a bug reporting, included are the output of various /proc file
> > > > on my system:
> > > >Motherboard: ASUS P2B-F with the latest bios bx2f113.aw
On Wed, 6 Sep 2000, Andrea Arcangeli wrote:
> The 2.2.18pre2aa1 patch is here:
>
>
>ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.18pre2aa2.bz2
It contains code in arch/i386/mtrr.c that looks pretty much like
my "64 bit MTRR" patch that was posted on lkml some ti
Michael Elizabeth Chastain wrote:
> (c) With separate source and build trees, which I've implemented,
> it becomes a lot more feaasible to manage kernel builds for
> multiple platforms.
Is this released? I build most of my kernels for both x86 and PowerPC,
plus I build several configurat
[EMAIL PROTECTED] said:
> It's the update to gcc2.96 causing this problems?? How can i get to
> compile the kernel?
You cannot safely compile even 2.4 kernels with gcc-2.96 on any platform, as
far as I'm aware. It's an insane thing to do. Use a sensible compiler.
--
dwmw2
-
To unsubscribe f
I've done an implementation of some of the Win32 "system calls" in a kernel
module in an attempt to speed up Wine.
The preliminary benchmarks that I made, while not very real-world since I
don't think I have managed to implement enough for that yet, seem to indicate
that in some tests, I can bea
[EMAIL PROTECTED] said:
> Which Linux companies are profitable? **NONE**. The only people
> making money are hardware vendors and it's a model like SUN's, where
> you get a free "machine driver" with every system you buy.
And nobody has explained to me why these are _bad_ things.
--
dwmw
David Howells wrote:
>
> I've done an implementation of some of the Win32 "system calls" in a kernel
> module in an attempt to speed up Wine.
Please by no way don't include this patch into the official tree.
It's insane due to the following:
1. Linux is UNIX not NT... (in terms of API)
2. WINE
Chris Wedgwood wrote:
>
> On Wed, Sep 06, 2000 at 12:52:29PM -0700, Linus Torvalds wrote:
>
> [... words of wisdom removed for brevity ...]
>
> I'm a bastard, and proud of it!
>
> Linus
>
> Anyone else think copyleft could make a shirt from this?
I like this
[EMAIL PROTECTED] said:
> So it seems to be a bug at least in terms of timing. Unfortunately I
> only got about 4 replies to the patches that touched 20+ drivers. I
> suppose I should just hassle maintainers until they fix it or tell me
> where I've gone wrong ...
Actually, I was quite happy c
On Thu, 7 Sep 2000, George Anzinger wrote:
> Chris Wedgwood wrote:
> >
> > On Wed, Sep 06, 2000 at 12:52:29PM -0700, Linus Torvalds wrote:
> >
> > [... words of wisdom removed for brevity ...]
> >
> > I'm a bastard, and proud of it!
> >
> > Linus
> >
> > Anyo
Gregory Maxwell wrote:
>
> On Wed, 6 Sep 2000, Alan Cox wrote:
>
> > > Ehh? And exactly _how_ would a debugger help it.
> > >
> > > Especially as Alan quoted an example of a driver bug that didn't get fixed
> > > for several months because the maintainer didn't have the hardware.
> > >
> > > Wha
Hi David,
> I'm also interested in finding a better way of getting to kernel space from
> user space... Currently, this involves the client process opening a proc file
> and doing ioctl's on it to request Win32 operations (easy to do from a kernel
> module).
how about the classical standard way
Ahmed El-Mahmoudy wrote:
>
> I read in Documentation/kmod.txt that kmod is preferred over kerneld, is
> 'kmod' a part of the linux kernel or is it a separate program like
> 'kerneld'? and if it is a separate program, from where can I download it
'kmod' is part of the kernel, its source is part of
> Please by no way don't include this patch into the official tree.
I wasn't intending to put it up for inclusion into the main kernel tree... I
think it is far better that it stays as a module, especially as it doesn't
require any changes to the main tree to be used, it can just be loaded when
> Q: Then why isn't kdb in the kernel?
> A: Uh...
More to the point, why don't the people that want a kernel
debugger maintain kdb and simply drop in the patch when they
need it? If Jeff releases his debugger will anyone care enough
to maintain it? Less talk, more action methinks :-).
Tigran Aivazian <[EMAIL PROTECTED]> wrote:
> how about the classical standard way of "getting to kernel space", i.e.
> plain system calls? Unless you really need a huge number of new system
> calls,
Just the one... this'll take a parameter specifying the Win32 call to make:
int win32(int f
Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote:
> We could use some more infrastructure here.
> (1) A 'make randomconfig' tool that generates a random configuration.
mconfig -m random, it's even written by you ;)
my current mconfig working version is on
ftp.openlinux.org/pub/people/hch/mc
Christer Weinigel wrote:
>
> [[EMAIL PROTECTED]] wrote:
>
> >I'm really kind of surprised that companies like SuSE, VA and RedHat
> >haven't started talking about forking the kernel already. Those companies
> >are serving the administrators and managers whose needs you are openly
> >admitting th
On Thu, 7 Sep 2000, Martin Dalecki wrote:
> 2. WINE in itself is barely usefull - even in fact non existant, since
> there is no official stable release out there.
Speak for yourself. Many people find it extremely useful; some depend on
it.
-Dan
-
To unsubscribe from this list: send the line "u
> On Thu, 7 Sep 2000, George Anzinger wrote:
>
> > Chris Wedgwood wrote:
> > >
> > > On Wed, Sep 06, 2000 at 12:52:29PM -0700, Linus Torvalds wrote:
> > >
> > > [... words of wisdom removed for brevity ...]
> > >
> > > I'm a bastard, and proud of it!
> > >
> > >
Respected colleagues!In advanced Unix systems, including
SCO UnixWare, SUN OS
there is a facility of transmission of descriptor of openning
file
through stream, by means of the command ioctl I_SENDFD.
For instance, following command writes transDsc descriptor to
the stream streamDsc.
On Thu, 7 Sep 2000, Martin Dalecki wrote:
> > I've done an implementation of some of the Win32 "system calls" in a kernel
> > module in an attempt to speed up Wine.
> 1. Linux is UNIX not NT... (in terms of API)
What about a Win32 personality?
> 2. WINE in itself is barely usefull - even in fa
Simon Richter wrote:
>
> On Thu, 7 Sep 2000, Martin Dalecki wrote:
>
> > > I've done an implementation of some of the Win32 "system calls" in a kernel
> > > module in an attempt to speed up Wine.
>
> > 1. Linux is UNIX not NT... (in terms of API)
>
> What about a Win32 personality?
>
> > 2. W
On Thu, 7 Sep 2000, Andrey G. Kaplanov wrote:
> Respected colleagues!
> In advanced Unix systems, including SCO UnixWare, SUN OS
> there is a facility of transmission of descriptor of openning file
> through stream, by means of the command ioctl I_SENDFD.
Linux has no streams. It's
On Thu, 7 Sep 2000, Andrey G. Kaplanov wrote:
> For instance, following command writes transDsc descriptor to the
> stream streamDsc.
> int ret = ioctl(streamDsc, I_SENDFD, transDsc);
> On Red Hat Linux kernel 2.2.16 ret is -1, errno is 22 - Invalid argument.
Implementing this ioctl for Li
Gregory Maxwell <[EMAIL PROTECTED]> wrote:
>If this is your primary argument for a kernel debugger, a 'crash dump tool
>with extra controls', then why not just cleanly implement a 'crash dump
>tool with extra controls'.
What about an enhanced printk tool that virtually inserts conditional
printk
also, omit nvram and wdt drivers from your list - I'll do them now.
Regards,
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
I have several systems (Siemens Scenic PRO D6 - P-II 233 - 64MB) running
with 4 asus (type 36) in the same irq. I had to modify the code to add the
shareable flag. No problem at all.
Regards.
==
Jorge Boncompte - Técnico de sist
Sorry I forget to say that this systems runs with stock 2.2.16 kernel.
(w6692.c v1.4)
Bye.
==
Jorge Boncompte - Técnico de sistemas
DTI2 - Desarrollo de la Tecnología de las Comunicaciones
--
Found another bug:
On Wed, Sep 06, 2000 at 03:26:14PM -0700, Linus Torvalds wrote:
> - pre6:
> - trunate - the never-ending story. Makes me feel like a long
^ here
:-)
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
On Wed, 6 Sep 2000, Horst von Brand wrote:
>Experts on legal stuff and copyright you won't find here, I'm afraid.
>
>May I ask why not GPLing the driver? You could for example state that the
>code is under GPL for use in the Linux kernel only,
Not possible. The GPL explicitly states that you ma
The ongoing saga of the machine that hates tuning being enabled;
2.4.0-test8-pre6
Boot message w/ PIIXn tuning enabled:
[...]
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 39
P
Hi to all,
What is the use of m68k_clone function ?. Will
linuxthreads library call this function in order to implement the pthreads
?.
please provide some details about
this.
with best regards,
Mahadev
Rats! Someone _did_ come up with something terrible. The ide-stuff
wasn't compiling at all. So after putting a big brown paper-bag over my
head and poking two holes in it to be able to see, I sat down with a
fresh tree and tried to compile every damn option. The result is a
2.0.39pre8 which probab
Linus and others,
Please take a look at the patch attached, and consider applying. It fixes
some of the OOM issues with sd.c and does general cleanups (module_init/exit,
removing casts, etc.).
I just searched the archives and found that Arnaldo Carvalho de Melo submitted
a similar patch for test
Hi guys,
Please have a look at this patch - if you find nothing wrong I will send
it to Linus later on.
It fixes:
a) bugfix to read_kmem() which currently can fail on low memory when it
should succeed (i.e. when it doesn't need that page)
b) nvram driver doesn't handle failures from misc_re
> Ugh. What rubbish.
>
> The moment I detect my provider changing anything beyond a TTL is the
> moment I find a new provider.
The 'problem' is a bunch of stupid American politics (excuse anyone
American), than passed a law that all spam containing a remove adress is
legal.
So that means I ge
Hi to all,
sorry for the inconvenience caused in previous mail.
plase cc to [EMAIL PROTECTED]
What is the use of m68k_clone function ?. Will linuxthreads library call
this function in order to implement the pthreads ?.
please provide some details about this.
with best regards,
Mahadev
-
To u
> 4.21, IIRC. Check the BUGTRAQ. Nobody had provided a full analysis, let
> alone exploit, but there was an example of headers making pine _very_
> unhappy (attempt to save the mailbox after any modifications => screwed
> mailbox). I didn't attempt to dig in the source - Mark et.al. got such a
>
Hi.
I have just gotten hold of an old machine previously running Win98. When
I tried to install RH 6.2 on it I got an oops during boot from the floppy.
I replaced the kernel on the floppy with a 2.4.0-test8-pre6 kernel and
got an oops again right after the line 'POSIX conformance testing by UNIFI
On Thu, 7 Sep 2000, David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > Which Linux companies are profitable? **NONE**.
That's a statement with balls, which I would really see with some
numbers..
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
[viro]
> > making the internal API frozen by exposure to library users.
[Gooch]
> An exercise in decent API design. BFD.
^^^
Nah, that's the *de*compilation library.
(Sorry, couldn't resist.)
Peter
-
To unsubscribe from this list: send the line "unsubscrib
I'd like to advocate the inclusion of the majority of these patches of
Andrea's. I've been patching most of them in for a while now simply
because I've found my SMP system much more stable and useable.
Distinctly lacking from the 2.2.17 release was Marcelo Tosatti's age-old
1-character fix to s
On Thu, Sep 07, 2000 at 07:45:48AM +0200, Luca Montecchiani wrote:
> > I think I prefer the current version over your patched version.
> > But will probably change my mind when many people complain.
>
> Why have *fdisk or lilo trouble ?
I don't know whether lilo has trouble. But if it has
that
Ok, more bothersome irk. =|
test8-pre4 was the last kernel the pegasus driver worked in. Since then
it refuses to go online. The code in the pegasus.c file hasn't changed,
so somebody in the middle broke. All the changes seem to have happened
in pre5. Here's what I've gleaned thusfar.
Message
On Thu, 7 Sep 2000, Boszormenyi Zoltan wrote:
>It contains code in arch/i386/mtrr.c that looks pretty much like
>my "64 bit MTRR" patch that was posted on lkml some time last year
>and makes use of the full 36 bit MTRR address and size on Intel and
>44 bits on AMD Athlon. BTW my patch contained s
Igmar Palsenberg <[EMAIL PROTECTED]> writes:
> The 'problem' is a bunch of stupid American politics (excuse anyone
> American), than passed a law that all spam containing a remove adress is
> legal.
No, they haven't. Some bill passed the house (or senate, I can't
remember) but it hasn't been p
Andi Kleen <[EMAIL PROTECTED]> wrote:
> It could use a read-only-to-clients shared memory with some locking tricks.
You still have to be able to emulate WaitForMultipleObjects() which I think is
quite difficult from userspace. It can perhaps be done with signals, but that
then incurs costs in inv
With all the talk of improving Linux's scalability to
large-scale SMP and ccNUMA platforms -- including efforts
at several HW companies and now OSDL forming to throw
hardware at the effort -- is there any move afoot to
coordinate these efforts?
The LSE project at sourceforge seems to have been
On Thu, Sep 07, 2000 at 02:28:36PM +0100, David Howells wrote:
> > I looked a bit over the code. Your Mutex classes do not look very SMP safe,
> > have they been tested with SMP ?
>
> Look carefully... It uses the atomic bit set/clear functions to modify the
> state, and the wait-queue carries it
On Wed, 6 Sep 2000, Dan Hollis wrote:
> On Wed, 6 Sep 2000, Alan Cox wrote:
> > For things like driver debugging its the only way to work. Hardware simply does
> > not work like the manual says and no amount of Zen contemplation will ever
> > make you at one with a 3c905B ethernet card.
>
> Th
Andi Kleen <[EMAIL PROTECTED]> wrote:
> I did not see the lock. Where is it ?
Well, on the bit functions set_bit() and test_and_clear_bit(), the macro
inserts an appopriate locking instruction into the assembly.
On the wait queue, the wait_queue structure includes
> I don't know too much abou
> Is it / will it be possible to run multiple, or at least two keyboards
> before the new linux console code in 2.5?
XFree86 can use multiple keybaords. I don't think XF4.0 still supports USB
keyboards. Give them another 6 months or a year. By then they should
support them. As for the console sy
[EMAIL PROTECTED] wrote:
>
> On 6 Sep 2000, Linus Torvalds wrote:
> > In article <[EMAIL PROTECTED]>,
> > Jeff V. Merkey <[EMAIL PROTECTED]> wrote:
> I guarantee you that IT managers and CTOs do not share your enthusiasm for
> slow, correct coding when faced with their business being down, their
"J. Dow" <[EMAIL PROTECTED]> said:
[...]
> The point is that WITH a debugger you have to take that step as well.
> A person without the self discipline to do that is still a child and should
> not be in this business. The debugger gives you a better picture of what
> is actually happening. If th
On Thu, Sep 07, 2000 at 02:44:26PM +0100, David Howells wrote:
>
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> > I did not see the lock. Where is it ?
>
> Well, on the bit functions set_bit() and test_and_clear_bit(), the macro
> inserts an appopriate locking instruction into the assembly.
But that
[viro]
> The _real_ problem is preprocessor abuse. BTW, could we schedule for
> 2.5 the following?
> * things like CONFIG_FOO are _always_ defined. As 0 or 1, that is.
> * #ifdef CONFIG_FOO => if (CONFIG_FOO) in *.c. gcc will kill the unused
> branches just fine.
Notwithstandin
> > Is it / will it be possible to run multiple, or at least two keyboards
> before the new linux console code in 2.5?
> It is a whole lot more complex than that.
> [snip]
> Consider a multihead enviroment with 2 users. Each VT is in
> console mode. One starts the X server. Automatically X wan
Alexander Viro <[EMAIL PROTECTED]> said:
[...]
> BTW, tools are really nice, but I wouldn't call conventional debuggers
> a-la [asg]db good ones. I've been _very_ impressed by Acid - after gdb it
> feels like a switch from MCR to sh. Small core providing a language with
> enough primitives to bu
On Wed, 6 Sep 2000, Jeff V. Merkey wrote:
> I have no axe to grind, but I do have a different view. I'm the 1 in 30
> million men born with an extra Y chromosone (a double YY), so you are
> pertially right there. DOuble YY males have a different brain structure
> -- the lymbic system in my brai
Hi Leonard,
this night I (hopefully) finally spotted and fixed a longstanding deadlock
that was hitting us on heavily loaded server running the DAC960.
The bug is present also in the earlier 2.2.x and 2.4.x and it's _not_ been
introduced with the DAC960 updates in 2.2.17.
In 2.4.x the SMP deadl
David Woodhouse wrote:
> You cannot safely compile even 2.4 kernels with gcc-2.96 on any platform, as
> far as I'm aware. It's an insane thing to do. Use a sensible compiler.
Oh. I've been using gcc-2.96 with test7 for a while, no problems except
the ## warnings. Never occured to me that gcc-2.
"make xconfig" failed in line 8 of fs/nls/Config.in.
---
#
# Native language support configuration
#
# msdos and Joliet want NLS
if [ "$CONFIG_JOLIET" = "y" -o "$CONFIG_FAT_FS" != "n" \
-o "$CONFIG_NTFS_FS" != "n" -o "$CONFIG_NCPFS_NLS" = "y" \
Linus Torvalds wrote:
> Yeah. Maybe we fixed truncate, and maybe we didn't. I've thought that
> we fixed it now several times, and I was always wrong. Time for some
> reverse phychology:
>
> I'm sure this one doesn't fix the truncate bug either.
So far things look really promising here. No ext2
If it is the 2.2.16 scheduler & other linux'es have a bug.
The following code snippets can go into a tight loop.
while (p != &init_task)
{
if (can_schedule(p))
{
int weight = goodness(prev, p, this_cpu);
if (weight > c)
c = weight, next = p;
}
Hello,
I am not sure if this is the right list to point out some linux TCP
implementation "weakness" but I think that something should be done
first at the kernel level and after with any other way (firewalling etc).
The problem:
I am using 2.0.38 and I am receiving lots of DoS attacks on one of m
Hi Linus,
This patch (courtesy of Eric W. Biederman <[EMAIL PROTECTED]>) allows
the microcode driver to make the correct decision about patch revision
even if there were no update done by the BIOS at all.
Regards,
Tigran
--- linux/arch/i386/kernel/microcode.c Thu Aug 24 08:08:43 2000
+++ work/
Hi Linus,
This patch was reviewed by human kind for several hours and there was
found no fault in it.
It fixes:
a) bugfix to read_kmem() which currently can fail on low memory when it
should succeed (i.e. when it doesn't need that page)
b) nvram driver doesn't handle failures from misc_regi
Test
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
I just found out that gcc-2.96 won't compile glibc-2.1.93 or glibc-2.1.2 or
glibc-2.1.3 successfully whereas gcc-2.95.2 will. It bombs in a couple of
places.
I just downgraded my machine to 2.95.2 to prove the point. Guess I'll wait
for gcc-3.0.
Michael
Andi Kleen <[EMAIL PROTECTED]> wrote:
> But that's not race free on SMP. Two CPUs can set the bit in parallel
> and you'll never notice. You would need at least a protecting spinlock
> between the test bit and set bit (or a cmpxchg on x86)
Are you sure? I understood that the "lock" prefix on a
-test7 was the first one I tried that actually booted, the rest just froze.
I only tried 2 kernels. The first was compiled with
CONFIG_ALPHA_LEGACY_START_ADDRESS set to n, and the 2nd was with y.
First was -test6
when booting -test7, it can't find any IRQs for the PCI devices.
This is an Alpha
On Thu, Sep 07, 2000 at 04:25:29PM +0100, David Howells wrote:
>
> Andi Kleen <[EMAIL PROTECTED]> wrote:
> > But that's not race free on SMP. Two CPUs can set the bit in parallel
> > and you'll never notice. You would need at least a protecting spinlock
> > between the test bit and set bit (or a
David Howells <[EMAIL PROTECTED]> schrieb / wrote am / at : 07.09.2000
16:25:29
>
> Hold on a moment... You said "between the test bit and set bit"... this is a
> single CPU instruction! With the lock prefix, there should be no between.
>
> Also, a quote from asm/bitops.h:
> - /*
> - * These hav
Hi,
In the past few days, a couple of our webservers (dual P3s)
have started to emit $SUBJECT into the kernel logs fairly
frequently:
Sep 7 06:41:04 web2 kernel: initial req->mss below 8
Sep 7 06:56:03 web2 last message repeated 18 times
Sep 7 07:56:04 web2 last message repeated 18 times
Sep
On Thu, 7 Sep 2000, Mike Jagdis wrote:
> > Q: Then why isn't kdb in the kernel?
> > A: Uh...
>
> More to the point, why don't the people that want a kernel
> debugger maintain kdb and simply drop in the patch when they
> need it? If Jeff releases his debugger will anyone care enough
> to maintai
Date: Thu, 7 Sep 2000 16:50:51 +0200 (CEST)
From: Andrea Arcangeli <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], Alan Cox <[EMAIL PROTECTED]>
X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc
Hi Leonard,
this night I (hopefully) finally spotted and fi
David Howells writes:
> I've done an implementation of some of the Win32 "system calls"
> in a kernel module in an attempt to speed up Wine.
Oh my. How dare you! I like it. :-)
> The preliminary benchmarks that I made, while not very real-world
> since I don't think I have managed to implement
We had some problems booting 2.4.0-test7, and discovered that Linux fell
into a panic while parsing the MP Configuration table. After some debugging,
we found that there are 4 Busses entries:
Bus #0 is PCI
Bus #1 is PCI
Bus #18 is XPRESS
Bus #19 is EISA
Unfortunately, the XPRESS bus parsing calls
On Thu, Sep 07, 2000 at 09:00:29AM -0700, Leonard N. Zubkoff wrote:
> WaitQueue_T WaitQueueEntry = { current, NULL };
> add_wait_queue(&Controller->CommandWaitQueue, &WaitQueueEntry);
> current->state = TASK_UNINTERRUPTIBLE;
> spin_unlock(&io_request_lock);
> schedule();
> current->sta
David Woodhouse wrote:
>
> [EMAIL PROTECTED] said:
> > So it seems to be a bug at least in terms of timing. Unfortunately I
> > only got about 4 replies to the patches that touched 20+ drivers. I
> > suppose I should just hassle maintainers until they fix it or tell me
> > where I've gone wrong
Andi Kleen <[EMAIL PROTECTED]> wrote:
> This is far from a single CPU instruction between the test_bit and the
> set_bit. Even with a single CPU instruction you would need a cmpxchg with
> retry BTW, to handle the case of multiple CPUs entering the instruction at
> the same time. The easiest fi
Doug Gilbert and I ran across
some weirdness in the way the block device queues are plugged/unplugged.
It turned up with some benchmarks of the SCSI generics driver - with the new
queueing code, the generics driver is inserting requests into the same queue
that block device requests a
[EMAIL PROTECTED] said:
> > If there's other stuff on the run queue, it won't return immediately,
> > will it?
> It most likely will return immediately.
Oh well in that case it ought to task its task to something other than
TASK_RUNNING...
> > Otherwise, it would be TASK_UNINTERRUPTIBLE.
>
On Thu, 7 Sep 2000, Tigran Aivazian wrote:
>
> k) all swapout functions in mm/vmscan.c can be optimized by removing 'mm'
>argument. This part was reviewed by Rick van Riel and approved.
But they then get "mm" themselves anyway.
What's the point? With argument passing, on certain architect
Tigran Aivazian writes:
> On Thu, 7 Sep 2000, George Anzinger wrote:
> > I like this one better:
> >
> > "And I'm right. I'm always right, but in this case I'm just a bit more
> > right than I usually am." -- Linus Torvalds, Sunday Aug 27, 2000.
> >
>
> I like this one even better:
>
> "Littl
On Thu, 7 Sep 2000, G. Hugh Song wrote:
> if [ "$CONFIG_JOLIET" = "y" -o "$CONFIG_FAT_FS" != "n" \
> -o "$CONFIG_NTFS_FS" != "n" -o "$CONFIG_NCPFS_NLS" = "y" \
> -o "$CONFIG_SMB_FS" != n ]; then
n vs "n" is my error.
However 'make menuconfig' works with just n. I know I should h
On Thu, 7 Sep 2000, Linus Torvalds wrote:
>
>
> On Thu, 7 Sep 2000, Tigran Aivazian wrote:
> >
> > k) all swapout functions in mm/vmscan.c can be optimized by removing 'mm'
> >argument. This part was reviewed by Rick van Riel and approved.
>
> But they then get "mm" themselves anyway.
>
Hello,
I am using a 3CCFE575CT with a Compaq Armada under the kernel 2.4.0-test7
and pcmcia-3.1.19. I am running Mandrake 7.0. The problem concerns the
cardmgr and/or the 3c59x kernel module. When the pcmcia service starts, it
initializes the cardmgr, reads the sockets, installs the proper kerne
On Thu, 7 Sep 2000, Leonard N. Zubkoff wrote:
>I tried retrieving that file but was unsuccessful; is that the correct URL?
I guess I cut and pasted too much directories, sorry. I attached the file
since it's small.
>Is the fix simply moving the spin_unlock right before the call to
>add_wait_que
Hello!
> tried to grep gcc but my gcc knowledge is too low to reverse engeneer the
> implement semantics of the "memory" clobber fast
Just hint. I remember the time when "memory" clobber option
was _absent_ in gcc. And we managed to compile kernel with such gcc. 8)
To all that I understand, "asm
** Reply to message from "J. Dow" <[EMAIL PROTECTED]> on Thu, 7 Sep 2000
02:50:37 -0700
> Aw, Tigran, give the kid his hobby, OK? We can try to bang some
> sense into his head and suggest ways his hobby could offer more
> satisfaction from good results achieved and make it more fun for
> the res
On Thu, 7 Sep 2000, Tigran Aivazian wrote:
> On Thu, 7 Sep 2000, Linus Torvalds wrote:
>
> >
> >
> > On Thu, 7 Sep 2000, Tigran Aivazian wrote:
> > >
> > > k) all swapout functions in mm/vmscan.c can be optimized by removing 'mm'
> > >argument. This part was reviewed by Rick van Riel and
On Thu, 7 Sep 2000, Andi Kleen wrote:
>On Thu, Sep 07, 2000 at 09:00:29AM -0700, Leonard N. Zubkoff wrote:
>> WaitQueue_T WaitQueueEntry = { current, NULL };
>> add_wait_queue(&Controller->CommandWaitQueue, &WaitQueueEntry);
>> current->state = TASK_UNINTERRUPTIBLE;
>> spin_unlock(&io_req
David Howells <[EMAIL PROTECTED]> said:
[...]
> Anyway, I though I could get away with it, but on reflection, perhaps
> not... If two threads of the same process try and issue ReleaseMutex()
> simultaneously on one mutex, then theoretically, one should succeed and the
> other fail, but given the
the "vm_mm->mm" was of course a typo and should be read as
"vma->vm_mm". Sorry.
On Thu, 7 Sep 2000, Tigran Aivazian wrote:
> On Thu, 7 Sep 2000, Tigran Aivazian wrote:
>
> > On Thu, 7 Sep 2000, Linus Torvalds wrote:
> >
> > >
> > >
> > > On Thu, 7 Sep 2000, Tigran Aivazian wrote:
> > > >
>
Hello!
> - Could there be some kind of handling for such packets (meaning TCP packets
> reaching at an unused port with ACK bit set - with no previous SYN etc packet)
> to avoid such DoS attacks? Is the same happening to newer kernels? If yes,
> should we just eat it and shut up (because th
On Thu, 7 Sep 2000 [EMAIL PROTECTED] wrote:
>BTW Look also into asm-i386/bitops.h and dummy cast to some crap there.
>Are you impressed? 8)
Yep 8). If we add "memory" such stuff could be removed I think. As far I
can see the object of such stuff is to cause gcc to say `I'm too lazy to
see exactl
Hello,
I have a Compaq Armada 7400 running Mandrake 7.0 with the kernel 2.4.0-test7
and the pcmcia-3.1.19. I have two PCMCIA sockets in my system and only one
seems to work. I can read the following information in the
/var/log/messages:
pcmcia: Linux PCMCIA Card Services 3.1.11
k
1 - 100 of 265 matches
Mail list logo
