Something like this was presented at OSDI, uh, year before last.. you might
check the Usenix webpage about this.
On 20 Apr 2001 [EMAIL PROTECTED] wrote:
> Suppose that an entry on any filesystem could be replaced by a symlink
> which pointed to a URL, and that an appropriate handler was
On Fri, 20 Apr 2001, Jeremy Fitzhardinge wrote:
>
> I kept the dget/put out caution and ignorance, but they're clearly
> problematic. I'm happy to drop them if holding dcache_lock is enough
> to keep the tree stable while I traverse it.
How does this patch look to you people?
It's untested,
On Fri, 20 Apr 2001, Paul Mackerras wrote:
> Brown-paper bag time...
>
> The patch I sent earlier didn't include the accompanying changes to
> if_ppp.h and ppp_channel.h. Here they are.
>
> Paul.
>
> diff -urN linux/include/linux/if_ppp.h pmac/include/linux/if_ppp.h
> ---
when I use make menuconfig on the /usr/src/linux directory which linux
was symbolic link to /usr/src/linux-2.4.3 , I can see menu , but when I
press space or enter key will exit menu and show follow message :
Menuconfig has encountered a possible error in one of the kernel's
configuration
On Fri, 20 Apr 2001, Fabio Riccardi wrote:
> I agree that comparing different hardware architectures is a tricky
> business, but you asked me to comment on some of the comparisons that
> you made...
well, those two systems looked similar enough. (same CPU speed and the
test is CPU limited in
[EMAIL PROTECTED] wrote:
>
>Where does write support for NTFS stand at the moment? I noticed that it's
>still marked "Dangerous" in the kernel configuration. This is important to me
>because it looks like I'll have to start using it next week. My office laptop
>is going to be "upgraded" from
[Cc: trimmed]
Russell King wrote:
>
[...]
>
> Generally it seems like diff needs to produce one more line of context, and
> most of these problems will go away. Yes, there will still be the odd
> problem, so then it becomes the "how much do you crank the setting" problem.
>
$ diff -6 ...
Disconnect wrote:
> Addendum to 1. So far everyone (at least on LKML) who has had the
> crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or
> kk266r, IIRC) mobo.
>
> Have we gotten any fix, other than not using K7 optimizations?
I think it has something to do with the BIOS
Suppose that an entry on any filesystem could be replaced by a symlink
which pointed to a URL, and that an appropriate handler was dispatched
for that URL. This would allow, for example, config files to point to
a different machine.
Right now we can accomplish this by mounting alternative file
Lee Leahu wrote:
>
> On Friday 20 April 2001 20:39, you wrote:
> > Lee Leahu <[EMAIL PROTECTED]> writes:
> > > would somebody be kind enough to explain why writing to
> > > the ntfs file system is extremely dangerous, and what are the
> > > developers doing to make writing to ntfs filesystem
On Friday 20 April 2001 20:39, you wrote:
> Lee Leahu <[EMAIL PROTECTED]> writes:
> > would somebody be kind enough to explain why writing to
> > the ntfs file system is extremely dangerous, and what are the
> > developers doing to make writing to ntfs filesystem safe?
>
> It's dangerous because
On Fri, Apr 20, 2001 at 03:53:45PM -0400, Alexander Viro wrote:
> > Why are we doing the mntget/dget at all? We hold the spinlock, so we know
> > they are not going away. Not doing the mntget/dget means that we (a) run
> > faster and (b) don't have the bug, because we don't need to put the damn
>
Lee Leahu <[EMAIL PROTECTED]> writes:
> would somebody be kind enough to explain why writing to
> the ntfs file system is extremely dangerous, and what are the
> developers doing to make writing to ntfs filesystem safe?
It's dangerous because NTFS is a proprietary format, and the full
rules
From: "Lee Leahu" <[EMAIL PROTECTED]>
> would somebody be kind enough to explain why writing to
> the ntfs file system is extremely dangerous, and what are the
> developers doing to make writing to ntfs filesystem safe?
My understanding of the situation is that writing to an NTFS volume is
Francois Cami wrote:
>
> Vibol Hou wrote:
> ...
>
> > Apr 17 16:10:12 omega kernel: eth0: Too much work in interrupt, status e401.
>
> I got that one too, PC is ASUS P2B-DS with two PII-350, 384MB RAM,
> 3C905B.
If you were getting this message occasionally, and if increasing the
would somebody be kind enough to explain why writing to
the ntfs file system is extremely dangerous, and what are the
developers doing to make writing to ntfs filesystem safe?
--
[EMAIL PROTECTED],
Open Source + Linux = Freedom
-
To unsubscribe from this list: send the line "unsubscribe
This patch (made against linux-2.4.4-pre5) makes several changes to the rwsem
implementation:
(1) It fixes the bug found by Andrea by changing how processes that are
waiting on the semaphore are managed.
(2) As a result of (1), the wake_up_ctx() stuff is no longer used and has
been
On 04.21 Alan Cox wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
gcc-2.96 spits warnings about possibly-used-before-initialized vars in
mtrr.c, line 2004:
static void __init centaur_mcr_init(void)
{
int lo,hi;
..
if (anything)
set hi,lo
Andreas Dilger <[EMAIL PROTECTED]>:
> One of the issues for contacting each MAINTAINER is that this information
> is out-of-line from the actual kernel tree. The other is that the
> description of what a maintainer is actually controlling is somewhat
> vague.
I strongly agree. I first tripped
Note: I'm not on this mailing list (for now, domain IP is changing).
Please email directly
1) I've noticed very high CPU load 3.00 running ./configure alone
2) some gnome applications (Gnome Mailcheck broke with 2.4.4-pre5)
3) Resolving local domains takes an awful long time (though netscape)
Alan Cox <[EMAIL PROTECTED]>:
> > Even supposing that's so, a 36% rate of broken symbols is way too high.
> > It argues that we need to do a thorough housecleaning at least once in
> > order to get back to an acceptably low stable rate.
>
> Many of your 'broken' symbols arent. We have no idea
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
You may well need to 'make clean' before building -ac8 as the GDT layout
has changed a little.
2.4.3-ac11
o Merge Linus
On Sat, Apr 21, 2001 at 02:27:08AM +0200, Jesper Juhl wrote:
> Hi,
>
> While compiling a 2.4.3 kernel on my Slackware 7.1 box (heavily updated
> to have the correct utils and so on) I noticed a warning during 'make dep'.
>
> This is the exact message:
>
> make[6]: Leaving directory
> Is there anything out there to test/benchmark MMX ops? (Preferably with
> reporting on MMX and equiv non-MMX ops, tunable memory bandwidth, etc.)
I wrote a set of programs to tune the MMX code. Arjan I suspect did similar
when he reoptimised the code for the newer Athlon. Simple stuff like
On Sat, 21 Apr 2001, Alan Cox did have cause to say:
> K7 optimisation basically enabled the MMX copy/clear code which adds 30-40%
> performance to those functions. It also materially ups the maximum memory
> bandwidth the processor will use which may be where the fun starts.
Not to be
> Oddness. Is it all on that same via chipset? (I have seen some reports of
> the same chipset working on other mobos.)
Variants of the VIA chipset. But I have reports of works/not working from
the same board even.
> Is there a way to enable everything-K7-except-MMX? (Or, for that matter,
> an
David Woodhouse <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] said:
> > Even supposing that's so, a 36% rate of broken symbols is way too
> > high. It argues that we need to do a thorough housecleaning at least
> > once in order to get back to an acceptably low stable rate.
>
> Accepted. Can we let
On Sat, 21 Apr 2001, Alan Cox did have cause to say:
> > Addendum to 1. So far everyone (at least on LKML) who has had the
> > crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or
> > kk266r, IIRC) mobo.
>
> Not quite all. Many have but I have other reports.
Oddness. Is it
Hi,
While compiling a 2.4.3 kernel on my Slackware 7.1 box (heavily updated
to have the correct utils and so on) I noticed a warning during 'make dep'.
This is the exact message:
make[6]: Leaving directory /usr/src/linux-2.4.3/drivers/isdn/eicon'
make -C hisax fastdep
md5sum: WARNING: 12 of
> testb %al, intr_pending
> jnz somewhere_away_to_handle_defered_interrupt
>
> And - of course - interrupt checks intr_lock in its entry and if it is
> zero, sets intr_pending and exits immediatelly.
And immediately gets called again. You have to mask the irq which is non trivial
> Addendum to 1. So far everyone (at least on LKML) who has had the
> crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or
> kk266r, IIRC) mobo.
Not quite all. Many have but I have other reports.
> Have we gotten any fix, other than not using K7 optimizations?
As far as I
> I was referring to the infamous CLI/STI combinations that are more
> analogous to spinlocks than anything you are talking about. spl levels are
> clean and transparent and have been doing a very nice job in helping to
> avoid race conditions in real unix systems for quite some time now.
It
> Where does write support for NTFS stand at the moment? I noticed that it's
> still marked "Dangerous" in the kernel configuration. This is important to
> me because it looks like I'll have to start using it next week. My office
> laptop is going to be "upgraded" from Windows 98 to 2000. Of
Addendum to 1. So far everyone (at least on LKML) who has had the
crash-immediatly-do-not-pass-go issues has been using an iwill kk266 (or
kk266r, IIRC) mobo.
Have we gotten any fix, other than not using K7 optimizations?
I'm willing to keep trying new patches, if necessary. (And for that
At 23:33 20/04/2001, Thomas Dodd wrote:
>[EMAIL PROTECTED] wrote:
> > Also, I'll have to recreate my Linux partitions after the
> upgrade. Does anyone
>
>Oll you should need is a boot floppy to get back into linux and fix
>the MBR (rerun lilo?) after the Windows install.
Rerunning lilo is
A SCHED_FIFO or SCHED_RR task with priority n+1 will not preempt a
running task with priority n. You need to give the higher priority task
a priority of at least n+2 for it to be chosen by the scheduler.
The problem is caused by reschedule_idle(), uniprocessor version:
if
At 23:08 20/04/2001, [EMAIL PROTECTED] wrote:
>Where does write support for NTFS stand at the moment? I noticed that
>it's still marked "Dangerous" in the kernel configuration.
It is extremely dangerous. Never use unless you are desperate. It creates
corrupt files and especially directories.
On Fri, 20 Apr 2001, Andrea Arcangeli wrote:
>
> While dropping the list_empty check to speed up the fast path I faced the same
> complexity of the 2.4.4pre4 lib/rwsem.c and so before reinventing the wheel I
> read how the problem was solved in 2.4.4pre4.
I would suggest the following:
- the
Pavel Machek <[EMAIL PROTECTED]> writes:
[...]
> > I'm wondering if that veto business is really needed. Why not reject
> > *all* APM rejectable events, and then let the userspace event handler
> > send the system to sleep or turn it off? Anybody au fait with the APM
> > spec?
>
> My thinkpad
In article <[EMAIL PROTECTED]>,
Olaf Titz <[EMAIL PROTECTED]> wrote:
>> Ehh.. I will bet you $10 USD that if libc allocates the next file
>> descriptor on the first "malloc()" in user space (in order to use the
>> semaphores for mm protection), programs _will_ break.
>
>Of course, but this is a
Thanks to all who offered suggestions, both on the list and privately. Rather
than answer them all individually, I'm going to respond in this one message.
Unfortunately the upgrade is not going to be done by me, but by our PC support
team. Our laptops originally were set up with two FAT32
Between 2.4.3-ac9 and 2.4.3-ac10 the CDROM Uniform Driver was modified.
The modification added a dependency of the *register_cdrom() functions
on the cdrom_init() function. Theoretically, cdrom_init() should have
been called before any call to register_cdrom(). But practically, when
the CDROM
> Even supposing that's so, a 36% rate of broken symbols is way too high.
> It argues that we need to do a thorough housecleaning at least once in
> order to get back to an acceptably low stable rate.
Many of your 'broken' symbols arent. We have no idea what the real amount is
-
To unsubscribe
On Fri, Apr 20, 2001 at 08:36:37AM -0400, Doug McNaught wrote:
[ not much at all spams at linux-kernel ... ]
>
> That's partly because davem and Matti are rabid anti-spam weasels and
> very good at it. ;) There are all kinds of filters (including
> content-based ones) on l-k, otherwise we'd be
On Fri, Apr 20, 2001 at 08:17:09PM +0200, Hans-Joachim Baader wrote:
> Hi,
>
> in case it isn't already known:
>
> isdn_net.c: In function `isdn_ciscohdlck_dev_ioctl':
> isdn_net.c:1455: structure has no member named `cisco_keepalive_period'
>
Fix was posted last night here.
--
Karsten Keil
[EMAIL PROTECTED] wrote:
>
> partition. The upgrade, though, will involve wiping the hard drive, allocating
> the whole drive to a single NTFS partition, and reinstalling Notes after
> installing Windows 2000 . That means bye-bye FAT32 partition and hello NTFS. I
> can't mount it read-only
[EMAIL PROTECTED] wrote:
>
> Where does write support for NTFS stand at the moment?
>
I'll let someone who knows about that answer that part ;)
> Also, I'll have to recreate my Linux partitions after the upgrade. Does anyone
> know if FIPS can split a partition safely that was created
"Eric S. Raymond" <[EMAIL PROTECTED]> writes:
> If there were already a library in ths stock Python distribution to
> digest .Xdefaults files I might consider this. Perhaps I'll write
> one.
No, please don't! .Xdefaults files as loaded by xrdb can contain cpp
directives which can depend on the
Where does write support for NTFS stand at the moment? I noticed that it's
still marked "Dangerous" in the kernel configuration. This is important to me
because it looks like I'll have to start using it next week. My office laptop
is going to be "upgraded" from Windows 98 to 2000. Of
"Richard B. Johnson" <[EMAIL PROTECTED]> writes:
> The kernel doesn't know if a process is going to use the FPU when
> a new process is created. Only the user's code, i.e., the 'C' runtime
> library knows.
Maybe you should try to understand the kernel code and the features of
the processor
[EMAIL PROTECTED] said:
> Even supposing that's so, a 36% rate of broken symbols is way too
> high. It argues that we need to do a thorough housecleaning at least
> once in order to get back to an acceptably low stable rate.
Accepted. Can we let the 2.4 "angry penguin"-enforced stabilising
<[EMAIL PROTECTED]> writes:
> Machine has been locking up between 0-3 times a day sporadically. Nothing
> predictable about it. Hadn't locked up for 3 days, and locked 3x today,
> the last 2 times within 20 minutes of each other. Had run stable with
> 2.2.18, and was running fairly stable on
David Woodhouse <[EMAIL PROTECTED]>:
> I'd be very surprised if the number of false positives isn't fairly stable,
> with new ones being introduced at a similar rate to the rate at which old
> ones finally become correct.
Even supposing that's so, a 36% rate of broken symbols is way too high.
[EMAIL PROTECTED] said:
> Not good enough. In a year, the pile of false positives would get
> high enough to make it too hard to spot real bugs like the Aironet
> mismatch. The whole point of the cleanup is to be able to mechanize
> the consistency checks so they require a minimum of human
Russell King writes:
> - Secondly, its very easy to miss stuff in the lkml hunk of email each
> day when you have less than 4 hours to read it and think about it.
> (note that architecture maintainers have to read mail from their
> side which may not be on lkml, think about that, think
David Woodhouse <[EMAIL PROTECTED]>:
> > Otherwise how can you distinguish between dead wood which must be
> > removed and potentially valid symbols referring to code existing only
> > in a remote tree?
>
> By periodically publishing a list of the potentially-obsolete symbols as ESR
> has done,
[EMAIL PROTECTED] said:
> Therefore it's the maintainer's job to submit coherent patches and
> accept to see inconsistent CONFIG_* references be removed from the
> official tree until further patch submission is due.
Maybe. But you tend to include the latest MTD code in your tree, for
example,
Ingo Molnar wrote:
> > On a Dell PowerEdge 1550/1000 the published TUX 2 result is 2765.
> >
> > If you take into account the fact that the 1550 has a faster processor
> > (1GHz) and a more modern bus architecture (Serverworks HE with memory
> > interleaving and a triple PCI bus), the
Alan,
SPEC connections are cumulative of static (70%) and dynamic (30%) pages, with the
dynamic using quite a bit of CPU (25%-30%) and the static pages dataset of several
(6-8) gigabytes.
The chromium server is actually much faster than thttpd and it is a complete web
server.
- Fabio
Alan
Machine has been locking up between 0-3 times a day
sporadically. Nothing predictable about it. Hadn't locked up for 3
days, and locked 3x today, the last 2 times within 20 minutes of each
other. Had run stable with 2.2.18, and was running fairly stable on 2.4.3
up until about last week.
> CONFIG_BINFMT_SOM: arch/parisc/config.in arch/parisc/defconfig
> Not used in code anywhere. Can you get rid of this one?
Its used in the parisc tree as are most of the others you see. You probably want
to simply skip processing arch/parisc
-
To unsubscribe from this list: send the line
> Incidentally the same server running on a kernel with a multiqueue scheduler
> achieves 1600 connections per second on the same machine, that was the original
> reason for my message for a better scheduler.
I get 2000 connections a second with a single threaded server called thttpd
on my
[EMAIL PROTECTED] said:
> Have you tried mailing [EMAIL PROTECTED] and asking to be added?
Yes.
[EMAIL PROTECTED] said:
> I'd be highly surprised if they said no to adding UML to the list if
> you mailed them a request to update the page.
Well, be surprised then. The reply from hpa was that
I have attached a question concerning using 4GB of memory on an SMP.
Thanks for the time,
Dave
SMP Not using all 4GB Ram Question:
-
I am using a Compaq Proliant 8500 SMP with 8 550 Mhz processors and 4GB of RAM.
Using Kernel
[not subbed to [EMAIL PROTECTED], please mail me
directly]
Hi all,
I'm having MAJOR problems with using a USB Zip 250 with Linux 2.4.3.
First thing I saw, is under 2.4.3-ac9, I have hotplug support and
/sbin/hotplug installed, and I plugged it in and it found the drive
(yay!). Then I mounted
Hi,
On Wed, Apr 18, 2001 at 06:45:40AM -0300, Marcelo Tosatti wrote:
> As far as I can see, you cannot guarantee that an inode which is unlocked
> _and_ clean (accordingly to the inode->i_state) is safely on disk.
>
> The reason for that are calls to sync_one() which write the inode
>
It looks to me like the kernel sets a trap for FP operations when a
process is switched in. Then when the process executes an FP op, the
kernel clears the trap and either loads the FP context or initializes
it, depending on whether it is the process' first FP operation. So no
help is need from
On Fri, Apr 20, 2001 at 08:54:29AM -0400, Eric S. Raymond wrote:
> CONFIG_KEYBOARD_L7200
> CONFIG_KEYBOARD_L7200_DEMO
> CONFIG_KEYBOARD_L7200_NORM
> CONFIG_SERIAL_L7200
> CONFIG_SERIAL_L7200_CONSOLE
> CONFIG_SERIAL_SA1100
> CONFIG_SERIAL_SA1100_CONSOLE
Nope.
> CONFIG_HOST_FOOTBRIDGE
Nope.
>
Matthew Wilcox <[EMAIL PROTECTED]>:
> Code not merged yet.
:
> it's old and needs to die properly. i haven't had time to fix that yet.
Thanks for the information. Actually the parisc tree is one of the ones
that leaks the fewest of these symbols...
--
On Friday 20 April 2001 18:45, Francois Romieu wrote:
> I assume nothing is overclocked or whatever
Nothing is overclocked.
> Could you try this patch (more output during the loop):
Tried it. The (lengthy) log is attached.
The interrupt is triggered when the other side initiates a request.
On Fri, Apr 20, 2001 at 03:47:43PM -0400, Eric S. Raymond wrote:
> CONFIG_BINFMT_SOM: arch/parisc/config.in arch/parisc/defconfig
>
> Not used in code anywhere. Can you get rid of this one?
Code not merged yet.
> CONFIG_DMB_TRAP: arch/parisc/kernel/sba_iommu.c
> CONFIG_FUNC_SIZE:
On Fri, 20 Apr 2001, Linus Torvalds wrote:
> Why are we doing the mntget/dget at all? We hold the spinlock, so we know
> they are not going away. Not doing the mntget/dget means that we (a) run
> faster and (b) don't have the bug, because we don't need to put the damn
> things.
>
> Comments?
Hi David,
please remove rwsem.o from the list of exported objects, if it is
not used.
Regards
Ingo Oeser
patch is as follows
--- lib/Makefile.orig Fri Apr 20 21:51:12 2001
+++ lib/MakefileFri Apr 20 21:51:19 2001
@@ -8,7 +8,7 @@
L_TARGET := lib.a
-export-objs := cmdline.o
Matthew Wilcox <[EMAIL PROTECTED]>:
> > Could I ask you to audit your tree and change the prefix on any
> > CONFIG_ symbols that are private over there? This would make life
> > easier for my auditing tools (kxref and Stephen Cole's ach script).
>
> I don't think we have any of those. We
Summary:
print bad BIOS maps (those containing overlaps in memory regions).
Kernel:
linux-2.4.3-ac10
Description:
This change informs the user when overlaping memory regions are
found in an e820 memory map. If overlaps are found, the mapping is
displayed and then an adjusted map
On 20 Apr 2001, Victor Zandy wrote:
>
> No dice. Your program does not fix the problem.
>
> If it were a hardware problem, I would expect the problem to occur
> under 2.4.2 as well as 2.2.*, and I would be surprised that we can
> consistently produce the behavior across our 64 node cluster.
On Fri, 20 Apr 2001, Fabio Riccardi wrote:
> X15 is the server I was referring to and as far as I can measure I get
> very much the same performance as TUX.
>
> On a Dell 4400 (933 MHz PIII, 2G of RAM, 5 9G disks) I get 2450
> connections/second.
(the unit is not "connections/second" but
On 20 Apr 2001, Ulrich Drepper wrote:
> "Richard B. Johnson" <[EMAIL PROTECTED]> writes:
>
> > If it "fixes" it, there is no problem with the FPU, but with the
> > 'C' runtime library which doesn't initialize the FPU to a known
> > state before it uses it.
>
> It's the kernel which initializes
The current chromium server is based on Apache 1.3, and it inherits its threading
limitations.
Incidentally the same server running on a kernel with a multiqueue scheduler
achieves 1600 connections per second on the same machine, that was the original
reason for my message for a better
On Fri, 20 Apr 2001, Roberto Nibali wrote:
> No, it's not a bug but thank you for this tip. It's just a put-on limitation
> in the driver itself:
>
> --- starfire.c~ Fri Apr 20 18:48:05 2001
> +++ starfire.cFri Apr 20 18:27:20 2001
> @@ -308,7 +308,7 @@
> void
"Richard B. Johnson" <[EMAIL PROTECTED]> writes:
> If it "fixes" it, there is no problem with the FPU, but with the
> 'C' runtime library which doesn't initialize the FPU to a known
> state before it uses it.
It's the kernel which initializes the FPU. This was always the case
and necessary to
No dice. Your program does not fix the problem.
If it were a hardware problem, I would expect the problem to occur
under 2.4.2 as well as 2.2.*, and I would be surprised that we can
consistently produce the behavior across our 64 node cluster. But we
are keeping the possibility in mind.
On Fri, Apr 20, 2001 at 12:50:05PM -0400, Eric S. Raymond wrote:
> Nicolas Pitre <[EMAIL PROTECTED]>:
> > Why not having everybody's tree consistent with themselves and have whatever
> > CONFIGURE_* symbols and help text be merged along with the very code it
> > refers to? It's worthless to have
On 20 Apr 2001, Victor Zandy wrote:
>
> Victor Zandy <[EMAIL PROTECTED]> writes:
> > We have found that one of our programs can cause system-wide
> > corruption of the x86 FPU under 2.2.16 and 2.2.17. That is, after we
> > run this program, the FPU gives bad results to all subsequent
> >
Hi,
On Fri, Apr 20, 2001 at 03:49:30PM +0100, Alan Cox wrote:
> There is a proposal (several it seems) to make 2.5 replace the conventional
> unix swap with a filesystem of backing store for anonymous objects. That will
> mean each object has its own vm area and inode and thus we can start
> Optimization use in select: If all "interesting" file id's are known
> to be below "n", then only the first "n" bits in a FD_ISSET need to
> be examined. As soon as the bits are scattered, it takes MUCH longer
> to check for activity
That's an optimization, not a correctness issue.
>
On Fri, 20 Apr 2001, Jeremy Fitzhardinge wrote:
>
> This is a fix for a potential deadlock in autofs4's expire routine.
It's wrong.
I don't think we should be able to do a mntput() _either_ inside the
spinlock. The filesystem should not "know" that mntput is safe.
For this reason I don't
On Fri, Apr 20, 2001 at 02:48:18PM -0400, Nicolas Pitre wrote:
>
>
> On Fri, 20 Apr 2001, Tom Rini wrote:
>
> > On Fri, Apr 20, 2001 at 12:35:12PM -0400, Nicolas Pitre wrote:
> >
> > > Why not having everybody's tree consistent with themselves and have whatever
> > > CONFIGURE_* symbols and
On Fri, Apr 20, 2001 at 09:23:47AM +0100, David Howells wrote:
> Andrea seems to have changed his mind on the non-inlining in the generic case.
I changed my mind because if you benchmark the fast path you will do it without
running out of icache (basically only down_* and up_* will be in the
On Fri, Apr 20, 2001 at 10:59:34AM -0400, Eric S. Raymond wrote:
> All right then. I'm going to send you a bunch of dead-symbol cleanup
> patches. I'll try to stay in the mainline code and out of the port
> trees. Would you please do me the kindness of telling me which ones
> can go in and
I ment to send this correspondence to the list.
It seems to be working much better now -- but is this
CLONE_FILES flag correct?
Is there a device to look at which does a kernel_thread on open,
and kills the thread on close (I'd like to see an example).
Thanks for the help...
Marty
- ---
> "Jeff" == Jeff Dike <[EMAIL PROTECTED]> writes:
Jeff> [EMAIL PROTECTED] said:
>> http://www.kernel.org/ has a list of architecture websites. Also
>> the CREDITS / MAINTAINERS files tend to list the people who are
>> involved.
Jeff> Except it's restricted to processor ports, which would
Victor Zandy <[EMAIL PROTECTED]> writes:
> We have found that one of our programs can cause system-wide
> corruption of the x86 FPU under 2.2.16 and 2.2.17. That is, after we
> run this program, the FPU gives bad results to all subsequent
> processes.
We have now tested 2.4.2 and 2.2.19.
On Fri, 20 Apr 2001, Tom Rini wrote:
> On Fri, Apr 20, 2001 at 12:35:12PM -0400, Nicolas Pitre wrote:
>
> > Why not having everybody's tree consistent with themselves and have whatever
> > CONFIGURE_* symbols and help text be merged along with the very code it
> > refers to? It's worthless to
On Fri, Apr 20, 2001 at 02:00:00PM -0500, Jeff Dike wrote:
> [EMAIL PROTECTED] said:
> > http://www.kernel.org/ has a list of architecture websites. Also the
> > CREDITS / MAINTAINERS files tend to list the people who are involved.
>
> Except it's restricted to processor ports, which would
I periodically experience major system slowdowns, which are
obviously network related because they instantly go away when I pull
out the network cable, and return when I put it back in. The
machine is not totally unresponsive, but nearly so. For example, if
I hit enter at a shell prompt, it may
On 20 Apr 01 at 8:54, Eric S. Raymond wrote:
Hi Eric,
> Networking:
>
> CONFIG_SPX
This one will come back sometime. Hopefully... It is removed
for now, as code does not work (and never did). But help
text looks reasonable.
> General:
>
> CONFIG_NCPFS_MOUNT_SUBDIR
> CONFIG_NCPFS_NDS_DOMAINS
On Fri, Apr 20, 2001 at 12:35:12PM -0400, Nicolas Pitre wrote:
> There is kind of a ridiculous situation here where people want to withhold
> their own changes in their own trees for all good reasons until it is mature
> and stable enough to be fed upstream in the appropriate way, while
Since upgrading to 2.4.4-pre5 my PCMCIA wireless network card no longer works.
Here's a snippet of the dmesg output from 2.4.4-pre5:
Linux PCMCIA Card Services 3.1.22
options: [pci] [cardbus] [pm]
Intel PCIC probe: not found.
ds: no socket drivers loaded!
However, it works fine in both
Daniel writes:
> To quote Oliver Twist: "Please, Sir, I want some more". How about a
> explanation of the significance of GOOD_OLD_REV, etc. In particular, I'm
> curious why CURRENT_REV is defined as GOOD_OLD_REV and not DYNAMIC_REV.
One thing that deserves mentioning (related to your
1 - 100 of 509 matches
Mail list logo
