In the discussion on "select bug", some people noted that select does not
wake up a process until the buffer is half full (or all full, or
whatever). Does this mean that if a small amount is written to the
device/pipe the process may never be woken? Or is there a time limit that
wakes up
The vma list lock can nest with i_shared_lock, as per Kanoj Sarcar's
note on mem-mgmt locks (Documentation/vm/locking), and currently
vma list lock == mm->page_table_lock.
But there appears to be some inconsistency in the hierarchy of these
2 locks. (By vma list lock I mean
On Sat, 4 Nov 2000, Alan Cox wrote:
> > sysv semaphores have a very unfortunate negative feature -- if the admin
> > kill -9's the server (impatient admins do this all the time) then you end
> > up leaving a semaphore lying around. sysvsem don't have the usual unix
>
> Umm they have SEM_UNDO.
Linus Torvalds wrote:
>
> No.
>
> Please use unserialized accept() _always_, because we can fix that.
>
> Even 2.2.x can be fixed to do the wake-one for accept(), if required.
> It's not going to be any worse than the current apache config, and
> basically the less games apache plays, the better
Pressed enter too soon.
/*
* Call device private open method
*/
ret = -ENODEV;
if (dev->open && try_inc_mod_count(dev->owner)) {
if ((ret = dev->open(dev)) && dev->owner)
__MOD_DEC_USE_COUNT(dev->owner);
On Sun, 05 Nov 2000 12:28:55 +1100,
Andrew Morton <[EMAIL PROTECTED]> wrote:
> CPU0 CPU1
>
>rtnl_lock()
> dev_ifsioc()
> dev_change_flags()
> dev_open();
>dev->open();
>vortex_open()
>
On Sat, Nov 04, 2000 at 02:24:00PM +0200, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Andi Kleen) wrote on 02.11.00 in
><[EMAIL PROTECTED]>:
>
> > again with a different syntax than gcc [I guess it would have been too easy
> > to just use the gcc syntax]
>
> One of the big problems in C99 was
Dominik Kubla writes:
> On Fri, Nov 03, 2000 at 11:33:10AM -0800, H. Peter Anvin wrote:
[about IBM's JFS and ext3 both wanting to put code in fs/jfs]
>> How about naming it something that doesn't end in -fs, such as
>> "journal" or "jfsl" (Journaling Filesystem Layer?)
>
> Why? I'd rather
Dominik Kubla wrote:
>
> On Fri, Nov 03, 2000 at 11:33:10AM -0800, H. Peter Anvin wrote:
> >
> > How about naming it something that doesn't end in -fs, such as
> > "journal" or "jfsl" (Journaling Filesystem Layer?)
> >
>
> Why? I'd rather rename IBM's jfs to ibmjfs and be done with it.
>
>
"David S. Miller" <[EMAIL PROTECTED]> writes:
>From: Philippe Troin <[EMAIL PROTECTED]>
>Date: 03 Nov 2000 19:53:04 -0800
>
>Yes I agree, mixing signed and unsigned arithmetic is evil... Doesn't
>gcc have a flag for unsafe signed/unsigned mixtures ?
>
>Would you consider
On Sun, Nov 05, 2000 at 12:28:55PM +1100, Andrew Morton wrote:
> Andi Kleen wrote:
> >
> > On Sat, Nov 04, 2000 at 12:07:34PM -0500, Jeff Garzik wrote:
> > > Andi Kleen wrote:
> > > > All the MOD_INC/DEC_USE_COUNT are done inside the modules themselves. There
> > > > is nothing that would a
Andrew Morton wrote:
>
> Perhaps the best thing to do here is to create a system-wide
> semaphore for module unloading. So we do a down()/up()
> in sys_delete_module() and do this in dev_open:
Yep. I think this is right. Jeff, this supersedes the
patch you sent to devem yesterday.
---
Followup to: <[EMAIL PROTECTED]>
By author:"Marco d'Itri" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Nov 02, "Stephen C. Tweedie" <[EMAIL PROTECTED]> wrote:
>
> >2.2 O_SYNC is actually broken too --- it doesn't sync all metadata (in
> >particular, it doesn't update the
While Jeff and I basically agree on the short-term
solution (if one is still needed, altho I'm not aware of
any init order problems in USB in 2.4.0-test10), my
recollection of Linus's preference (without
looking it up) is to remove the calls from init/main.c
and to use __initcalls.
~Randy
>
Andi Kleen wrote:
>
> On Sat, Nov 04, 2000 at 12:07:34PM -0500, Jeff Garzik wrote:
> > Andi Kleen wrote:
> > > All the MOD_INC/DEC_USE_COUNT are done inside the modules themselves. There
> > > is nothing that would a driver prevent from being unloaded on a different
> > > CPU while it is already
Hi,
I found that Linux 2.4.x got locking with apm.o and yenta_socket.o
since yenta driver was there. But, someone has reported another apm.o
related locking. I don't know about why this problem causes and who
works for this.
So, I want more infomations, i.e. situation, position, timing and so
On Sat, Nov 04, 2000 at 12:07:34PM -0500, Jeff Garzik wrote:
> Andi Kleen wrote:
> > All the MOD_INC/DEC_USE_COUNT are done inside the modules themselves. There
> > is nothing that would a driver prevent from being unloaded on a different
> > CPU while it is already executing in ->open but has
On Sun, Nov 05, 2000 at 10:57:57AM +1100, Andrew Morton wrote:
> Even the DG/UX manpage doesn't say what happens when you sidegrade
> the lock. LOCK_EX->LOCK_EX :)
Suggested code:
printk("Don't do that\n"); return -EKNUCKLEHEAD;
--
It has been at least 2 days since the last message I received...
--
Mathieu CHOUQUET-STRINGER E-Mail : [EMAIL PROTECTED]
Learning French is trivial: the word for horse is cheval, and
everything else follows in the same way.
-- Alan J.
Alan Cox wrote:
>
> > have got it right. Does anyone know what this part of the
> > flock(2) manpage means?
> >
> >A single file may not simultaneously have both shared and
> >exclusive locks.
>
> AFAIK its saying LOCK_EX is exclusive and blocks shared locks and vice
> versa.
Hello Rik,
I've got a kernel oops with the 'latest' linux kernel and the DRI.
CD mounting was involved.
ksymoops 2.3.4 on i686 2.4.0-test10. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.0-test10/ (default)
-m
Brad Corsello wrote:
>
> [1.] One line summary of the problem:
> kernel oops on boot in 2.4.0 test 10 (i386)
>
> [2.] Full description of the problem/report:
> On every boot of test 10, I get a kernel oops very early on.
> Is reproducible (happens every boot).
>
I am trying to get an up-to-date stable kernel (2.2.18pre19, with
PowerPC changes, downloaded from the PowerPC BitKeeper archive)
compiled with the international patch (patch-int-2.2.17-9 which is the
latest in the crypto/ directory). The patch applies fine (with some
offsets, but all hunks
On Fri, Nov 03, 2000 at 06:51:05AM -0800, David S. Miller wrote:
>Are you saying that the original bug report may not actually be a
>problem? Is ms->rss actually protected in _all_ of the right
>places, but people got confused because of the syntactic sugar?
>
> I don't know if all
Since f_pos of struct file is a loff_t, on 32-bit architectures it
needs a lock to make accesses atomic (or some more sophisticated form
of protection). But looking in 2.4.0-test10, there doesn't seem to be
any such lock.
The llseek op is called with the Big Kernel Lock, but unlike in 2.2,
the
Hi,
i am getting
Nov 4 21:50:22 napalm kernel: Adding Swap: 48188k swap-space (priority -1)
Nov 4 21:50:25 napalm kernel: fbcon_setup: No support for fontwidth 12
Nov 4 21:50:25 napalm kernel: fbcon_setup: type 0 (aux 0, depth 8) not supported
Nov 4 21:50:25 napalm kernel: fbcon_setup: No
[1.] One line summary of the problem:
kernel oops on boot in 2.4.0 test 10 (i386)
[2.] Full description of the problem/report:
On every boot of test 10, I get a kernel oops very early on.
Is reproducible (happens every boot).
I've successfully booted 2.3 kernels
Thanks for the bug report, we'll investigate.
Hans
Tigran Aivazian wrote:
>
> Hi Hans,
>
> Simply starting the validation phase of SPEC SFS with NFS mounted reiserfs
> filesystem panics as shown in the log below. A quick look at the source
> suggests that _get_block_create_0() (and therefore,
hi,
here's a patch to make the channel bonding driver not try to
transmit on links that are down. there was a patch made to
2.3.x to do this via checking netif_carrier_ok(). this adds
the functionality to the 2.2.x driver code.
please cc: me in response.
brien
---
[Jeff V. Merkey <[EMAIL PROTECTED]>]
> I got a little further with the lock up problem, and it is related to
> MPS reporting a 2nd processor being present in some PPro systems when
> in fact only one CPU is really installed (but MPS is reporting
> default table entry 6 with a second CPU as
> sysv semaphores have a very unfortunate negative feature -- if the admin
> kill -9's the server (impatient admins do this all the time) then you end
> up leaving a semaphore lying around. sysvsem don't have the usual unix
Umm they have SEM_UNDO. Its a case of deeper magic
-
To unsubscribe
> > Instead, if apache had just done the thing it wanted to do in the first
> > place, the wake-one accept() semantics would have happened a hell of a
> > lot earlier.
>
> counter-example: freebsd had wake-one semantics a few years before linux.
And Im sure apache authors can use the utsname()
On Fri, Nov 03, 2000 at 08:33:36PM -0600, Peter Samuelson wrote:
>
> [Jeff Merkey]
> > Is this what is causing the lockup problems on 2.4.0-pre-10 with
> > PPro, or something else. Looks like something else.
>
> Yeah, it does, doesn't it. If this particular patch cured a
> kernel-side lockup
Keith Owens writes:
> Move this to "in progress" and add MTD code breaks with
> CONFIG_MODVERSIONS, for the same reason. I wrote a patch to replace
> get_module_symbol a week ago and sent it to the DRM/AGP/MTD people for
> testing - no response yet.
I have a fix likewise for the MTD code, so
[yes I feed trolls sometimes, it's fun]
[Taco Witte]
> Some days ago, I read about the idea of a completely modular kernel.
> I think it's a very good idea, because it would make it easier to get
> more people work at the same moment, development would go faster.
I contend that the barrier to
http://www.zabbo.net/maestro3/
contains a driver for the maestro3 and allegro chipsets that I'm fairly
happy with.
its 2.2 only for now, play with 2.4 at your own risk. for now it
includes its own ac97_codec.c that is backported from 2.2.
I expect playback to work as well as ac97 mixing. apm
FORT David <[EMAIL PROTECTED]> writes:
> Taco Witte wrote:
> > I think it's a very good idea, because it would make it easier to
> > get more people work at the same moment, development would go
> > faster. It would be possible to make groups for a certain part of
> > the kernel (for example
On Sat, 4 Nov 2000, Andrew Morton wrote:
> Dean,
>
> neither flock() nor fcntl() serialisation are effective
> on linux 2.2 or linux 2.4.
i have to admit the last time i timed any of the methods on linux was in
2.0.x days. thanks for the updated data!
> For kernel 2.2 I recommend that Apache
Taco Witte wrote:
> Hello
>
> Some days ago, I read about the idea of a completely modular kernel.
> I think it's a very good idea, because it would make it easier to get more
> people work at the same moment, development would go faster. It would
> be possible to make groups for a certain part
Hi Rik,
Rik van Riel <[EMAIL PROTECTED]> writes:
> Indeed, shared memory performance still sucks rocks.
No, it's not a performance problem. It is a hard lockup problem on
highmem machines.
I do see two problems here:
1) shm_swap_core does not handle the failure of prepare_higmem_swapout
On Fri, 3 Nov 2000, Linus Torvalds wrote:
> Please use unserialized accept() _always_, because we can fix that.
i can unserialise the single socket case, but the multiple socket case is
not so simple.
the executive summary is that when you've got multiple sockets you have to
use select().
On Sat, Nov 04, 2000 at 07:27:58PM +0530, [EMAIL PROTECTED] wrote:
> after reaching process count something around 30568, processes start
> getting pid from start, which ever is the first free entry slot in process
> table. that means we can't have simultaneously more than roughly 2^15
>
Hi all,
I'm trying to read application id, volume id and stuff from cds, but
don't figure out how to do it. It looks like ioctls CDROMREADMODE1 /
CDROMREADMODE2 may be the way to do it, but the kernel show a read error
when i try to read the data. What is needed in the struct cdrom_read to
Hello!
> de4x5 is becoming EISA-only in 2.5.x too, since its PCI support is
> duplicated now in tulip driver.
Luckily, my old Multia died. 8)
Jeff, tulip did not work with genuine Digital cards.
de4x5 was faulty (link state machine was broken, it has lost
link after some events on wire) but it
Jeff Garzik writes:
> Putting a call into init/main.c isn't a long term solution, but it
> should get us there for 2.4.x... init/main.c is also the best solution
> for ugly cross-directory link order dependencies. I would say the link
> order of foo.o's in linux/Makefile is the most
> have got it right. Does anyone know what this part of the
> flock(2) manpage means?
>
>A single file may not simultaneously have both shared and
>exclusive locks.
AFAIK its saying LOCK_EX is exclusive and blocks shared locks and vice
versa. Its a standard reader-writer lock
> after reaching process count something around 30568, processes start
> getting pid from start, which ever is the first free entry slot in process
> table. that means we can't have simultaneously more than roughly 2^15
> processes?
Yes
-
To unsubscribe from this list: send the line
On Sat, Nov 04, 2000 at 05:59:21PM +, Alex Buell wrote:
> I'm getting this problem each time I start pppd whenever I dial up if the
> ppp modules have been unloaded from memory. The odd thing is that I can
> repeat 'ppp-on' and it will work fine!
Another odd thing is that I have the same
Hi Linus,
This patch (against 2.4.0-test10) fixes the O_SYNC/ENOSPC bug. Alan Cox
included a fix for this same bug in 2.2.18pre7 and David Weinehall in
2.0.39final. This bug is listed on Ted's "Linux 2.4 Status / TODO page" as
"Fix Exists But Isnt Merged", "Writing past end of removeable device
tahallah[alex]:/home/alex > ppp-on
tahallah[alex]:/home/alex > /usr/sbin/pppd: This system lacks kernel
support for PPP. This could be because the PPP kernel module could not be
loaded, or because PPP was not included in the kernel configuration. If
PPP was included as a module, try
[EMAIL PROTECTED] (Tim Riker) wrote on 04.11.00 in <[EMAIL PROTECTED]>:
> Others that are commenting on the slow progress of some features in gcc
> should consider for themselves whether this position benefits the Open
> Source community or not.
Slow progress in gcc?
You know, I currently
[EMAIL PROTECTED] (Andi Kleen) wrote on 02.11.00 in
<[EMAIL PROTECTED]>:
> again with a different syntax than gcc [I guess it would have been too easy
> to just use the gcc syntax]
One of the big problems in C99 was that there was nobody on the committee
who really understood gcc well, so
[EMAIL PROTECTED] (Gábor Lénárt) wrote on 03.11.00 in
<[EMAIL PROTECTED]>:
> On Thu, Nov 02, 2000 at 02:27:35PM -0700, Tim Riker wrote:
> > #pragma is a particularly difficult problem to deal with because it is
> > non macro friendly. =(
> >
> > Sounds like C99 initializers are a likely first
[EMAIL PROTECTED] (Tim Riker) wrote on 02.11.00 in <[EMAIL PROTECTED]>:
> 1. C++ style comments
>
> Occurs in over 4000 lines of source and header files. :-( Should be
> converted to ansi c comments? We will probably want to just skirt this
> issue for now as the next rev of ANSI C is likely to
[EMAIL PROTECTED] (Alan Cox) wrote on 02.11.00 in
<[EMAIL PROTECTED]>:
> > How can I insure that the largest possible amount of my efforts benefit
> > the community at large? Hopefully this will make it easier to move to
> > C99 or any other future compiler porting project.
>
> The asm I dont
[EMAIL PROTECTED] (Christoph Hellwig) wrote on 02.11.00 in
<[EMAIL PROTECTED]>:
> In article <[EMAIL PROTECTED]> you wrote:
> > As is being discussed here, C99 has some replacements to the gcc syntax
> > the kernel uses. I believe the C99 syntax will win in the near future,
> > and thus the
Hi all,
after reaching process count something around 30568, processes start
getting pid from start, which ever is the first free entry slot in process
table. that means we can't have simultaneously more than roughly 2^15
processes?
am i correct?
regards,
Anil
-
To unsubscribe from this list:
[1.] Kernel 2.4.0-test10 does not boot
[2.] I installed 2.4.0-test10 in the same manner and on the same disk
I did with 2.4.0-test8 which boots an runs.
I use an ASUS-P2B-DS with 2xPII-350 and BIOS 1013BETA005.
After rebooting the last message is "Uncompressing the kernel .." and
then the system
On Sat, 4 Nov 2000, Alan Cox wrote:
>
> > Even 2.2.x can be fixed to do the wake-one for accept(), if required.
>
> Do we really want to retrofit wake_one to 2.2. I know Im not terribly keen to
> try and backport all the mechanism. I think for 2.2 using the semaphore is a
> good approach.
Andi Kleen wrote:
> All the MOD_INC/DEC_USE_COUNT are done inside the modules themselves. There
> is nothing that would a driver prevent from being unloaded on a different
> CPU while it is already executing in ->open but has not yet executed the add
> yet or after it has executed the _DEC but it
Serial driver in 2.4.0-testx seems to be a little broken.
Works fine with modem, mouse etc, but want works with
Casio digital camera - communication random hangs up
durning geting photos from camera.
It was tested on few computers with QV 780 and gphoto.
Evertything works fine with 2.2 kernel.
On Sat, Nov 04, 2000 at 10:36:36AM -0500, Jeff Garzik wrote:
> Andi Kleen wrote:
> >
> > On Sat, Nov 04, 2000 at 04:45:33AM -0500, Jeff Garzik wrote:
> > >
> > > > * What about dev->open and dev->stop ?
> > >
> > > Sleep all you want, we'll leave the light on for ya.
> >
> > ... but make
This patch (from Andreas Schwab <[EMAIL PROTECTED]>) makes macro expansion in
safer.
diff -u --recursive --exclude-from=/home/geert/diff-excludes-linux --new-file
linux-2.4.0-test10/include/linux/highuid.h
test/linux-merge11-2.4.0-test10/include/linux/highuid.h
---
Elmer Joandi wrote:
>
> At mandrake bootup, both isapnp and 3c509 as modules
http://gtf.org/garzik/kernel/files/patches/2.4/2.4.0-test10/3c509-fix-2.4.0.10.patch.gz
You need this patch for 3c509 to work as a module in 2.4.0-test10...
--
Jeff Garzik | Dinner is ready when
Building
At mandrake bootup, both isapnp and 3c509 as modules
Nov 4 20:29:46 news kernel: isapnp: Scanning for Pnp cards...
Nov 4 20:29:46 news kernel: isapnp: No Plug & Play device found
Nov 4 20:29:46 news kernel: Unable to handle kernel NULL pointer dereference at
virtual address 0070
Nov
Andi Kleen wrote:
>
> On Sat, Nov 04, 2000 at 04:45:33AM -0500, Jeff Garzik wrote:
> >
> > > * What about dev->open and dev->stop ?
> >
> > Sleep all you want, we'll leave the light on for ya.
>
> ... but make sure you have no module unload races (or at least not too
> huge holes, some
Russell King wrote:
> There'll be quite a few extra init calls going in there then, with lots
> and lots of ifdefs ;(
I was talking about one or two init/main.c additions. If you know of
"quite a few" link order problems outside of main USB subsystem init,
speak up...
Jeff
--
Jeff
On Sat, Nov 04, 2000 at 05:02:32AM +0200, Elmer Joandi wrote:
> under serious memory shortage, memory hog running and doing random access
> over 133 MB(128MB ram) and disk output as fast as it could.
> swap(128M) free = 0M, stable high disk io for long time, then
> me killing X with -9 , got
Hello
The old problem with smbfs and listing directories continue. The change of
infolevel that was thought to fix things in 2.2.14 didn't fix everything.
Here is a patch for another thing smbfs doesn't really do right,
apparently.
There is a mismatch between the negotiated maximum transfer
under serious memory shortage, memory hog running and doing random access
over 133 MB(128MB ram) and disk output as fast as it could.
swap(128M) free = 0M, stable high disk io for long time, then
me killing X with -9 , got oops.
/home is on reiserfs, which is on raid, which has 5 slices all on
Gentlemen,
Here's a patch which fully multithreads the file locking code.
The functionality is unchanged, however I wonder if we actually
have got it right. Does anyone know what this part of the
flock(2) manpage means?
A single file may not simultaneously have both shared and
Bug description
1. swapoff is broken with 2.4.0-test10 (swapped programs crash)
2. Boot with mem=64M boot parameter (or take a computer with only 64 meg of
RAM). Use a 64M swap partition. Launch several programs (for instance, start
StarOffice on KDE 2.0 + an xterm). su root on the xterm and
Hello
Some days ago, I read about the idea of a completely modular kernel.
I think it's a very good idea, because it would make it easier to get more
people work at the same moment, development would go faster. It would
be possible to make groups for a certain part of the kernel (for example
On Fri, Nov 03 2000, Stanislav Brabec wrote:
> Description:
> On 2.4.0-pre9 and 2.4.0-pre10:
> Playing of some audio CD's stops in nearly regular places. Also pressing
> >> in CD software panel in nearly all cases ends by stop.
Known problem, patch not submitted yet.
--
* Jens Axboe <[EMAIL
On 3 Nov 2000, Christoph Rohland wrote:
> On Wed, 1 Nov 2000, Rik van Riel wrote:
> > The 2.4 VM is basically pretty good when you're not
> > thrashing and has efficient management of the VM until
> > your working set reaches the size of physical memory.
> >
> > But once you hit the thrashing
--
/ \ Adam "[SzYnA]" Szendzielorz, administrator civ.pl,
| Phone/SMS: +(48) 60446,
| E-mail: [EMAIL PROTECTED] (buisness), [EMAIL PROTECTED] (priv)
\ / www.konta.pl - najtansze konta w calym Internecie !
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
[Nitin Dhingra]
> I had got your mail from redhat.com and came to know you are
> working under drivers in Linux.
What you got was a mailing list of probably tens of thousands of
subscribers. Some of us are working on drivers, some are not.
> I am working in a project that involves making a
> This is also a nice thought, but there is an obstacle.
> The Pro64 tools are Open Source and GPLed:
>
> http://oss.sgi.com/projects/Pro64/
>
> SGI retains the copyright to the code.
>
> As far as I know, the FSF owns the copyright to all code in the gcc
> suite. If improvements were taken
On Fri, 3 Nov 2000 17:54:51 -0500 (EST),
"Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
>(1)I have SCSI modules that have to be installed upon boot
>from initrd. Insmod failed with "Can't find the kernel version that
>this module was compiled with..."
"Can't find the kernel version that
> Even 2.2.x can be fixed to do the wake-one for accept(), if required.
Do we really want to retrofit wake_one to 2.2. I know Im not terribly keen to
try and backport all the mechanism. I think for 2.2 using the semaphore is a
good approach. Its a hack to fix an old OS kernel. For 2.4 its not
Description:
On 2.4.0-pre9 and 2.4.0-pre10:
Playing of some audio CD's stops in nearly regular places. Also pressing >> in CD
software
panel in nearly all cases ends by stop.
All these stops are reported:
Nov 3 21:41:47 utx kernel: ATAPI device hdb:
Nov 3 21:41:47 utx kernel: Error:
On Fri, 3 Nov 2000 10:09:31 -0500,
[EMAIL PROTECTED] wrote:
>9. To Do
> * DRM cannot use AGP support module when CONFIG_MODVERSIONS is
> defined (issue with get_module_symbol caused fix proposed by John
> Levon to be rejected)
Move this to "in progress" and add MTD code breaks
Respected Sir,
I had got your mail from redhat.com and came to know you are
working under drivers in Linux. I am also working in this field,
I would like you to help me out with one problem as I am stuck here
and couldn't proceed further.
I am working in a project that involves making a
On Sat, Nov 04, 2000 at 04:45:33AM -0500, Jeff Garzik wrote:
>
> > * What about dev->open and dev->stop ?
>
> Sleep all you want, we'll leave the light on for ya.
... but make sure you have no module unload races (or at least not too
huge holes, some are probably unavoidable with the
"Hen, Shmulik" wrote:
> We are trying to port a network driver from 2.2.x to 2.4.x and have some
> question regarding locks.
> According to the kernel locking HOWTO, we have to take extra care when
> locking between user context threads and BH/tasklet/softIRQ,
> so we learned (the hard way ;-)
Thomas Molina wrote:
> I want to make a minor change to the sound drivers Makefile for
> compiling pas16 as well as a modification to the documentation
> file. I'm told that since it is not a bugfix it needs to wait for post
> 2.4 final release.
Send me the patch... if its minor and useful,
This is also a nice thought, but there is an obstacle.
The Pro64 tools are Open Source and GPLed:
http://oss.sgi.com/projects/Pro64/
SGI retains the copyright to the code.
As far as I know, the FSF owns the copyright to all code in the gcc
suite. If improvements were taken from the Pro64
On Fri, Nov 03, 2000 at 06:57:32PM -0500, Jeff Garzik wrote:
> Andi Kleen wrote:
> > de4x5 is stable, but tends to perform badly under load, mostly because
> > it doesn't use rx_copybreak and overflows standard socket buffers with its
> > always MTU sized skbuffs.
>
> One of the reasons that
Maybe this got ignored because the subject was test9 oops when test 10 had
been released, or people tend to ignore .edu addresses...
> Just a note that this oops still occurs in test10. The problem occurs
> because get_devfs_entry_from_vfs_inode in devfs_follow_link (and/or
> devfs_read_link),
Michael Meissner <[EMAIL PROTECTED]> writes:
> On Fri, Nov 03, 2000 at 10:19:12PM -0800, Russ Allbery wrote:
>> May I tentatively suggest that one point at which your resources could
>> productively be applied is towards improving the C99 compliance in gcc?
>> Clearly for the near to medium
David Hammerton wrote:
>
> Hi,
>
> i just installed the latest kernel (2.4-test10).
>
> On recompilation of my "Nvidia" kernel drivers (for geforce 2 3d video support
> in linux), it failed linking to "mem_map_inc_count" (and dec_count).
>
> Im not much of a programmer, but to get it working
Hello,
On Sat, 4 Nov 2000, Andrea Arcangeli wrote:
> On Sat, Nov 04, 2000 at 01:09:42AM +, Julian Anastasov wrote:
> > Something like the attached old patch for 2.2. It is very
>
> It's not ok for 64bit archs.
Agreed. I see very different definitions for
On Fri, Nov 03, 2000 at 10:19:12PM -0800, Russ Allbery wrote:
> Tim Riker <[EMAIL PROTECTED]> writes:
>
> > Agreed. C99 does not replace all the needed gcc features. We should
> > start using the ones that make sense, and push for
> > standardization/documentation on the rest.
>
> > I'm
Ingo Oeser wrote:
>
> On Fri, Nov 03, 2000 at 10:12:31PM -0500, Jeff Garzik wrote:
> > But if you are going to eliminate info->vxi_base, it seems like that
> > would flush out all direct de-refs, whether they are buried in an
> > obscure macro or not. And if you find all that crap, you might as
Hi,
i just installed the latest kernel (2.4-test10).
On recompilation of my "Nvidia" kernel drivers (for geforce 2 3d video support
in linux), it failed linking to "mem_map_inc_count" (and dec_count).
Im not much of a programmer, but to get it working all i had to do was to add
to
Russell King wrote:
>
> Dunlap, Randy writes:
> > David is entitled to his opinion (IMO).
> > And I dislike this patch, as he and I have already discussed.
> >
> > Short of fixing the link order, I like Jeff's suggestion
> > better (if it actually works, that is): go back to the
> > way it was
On Fri, Nov 03, 2000 at 10:12:31PM -0500, Jeff Garzik wrote:
> But if you are going to eliminate info->vxi_base, it seems like that
> would flush out all direct de-refs, whether they are buried in an
> obscure macro or not. And if you find all that crap, you might as well
> use readb/writel at
On Sat, 4 Nov 2000, Andrew Morton wrote:
Dean,
neither flock() nor fcntl() serialisation are effective
on linux 2.2 or linux 2.4.
i have to admit the last time i timed any of the methods on linux was in
2.0.x days. thanks for the updated data!
For kernel 2.2 I recommend that Apache
sysv semaphores have a very unfortunate negative feature -- if the admin
kill -9's the server (impatient admins do this all the time) then you end
up leaving a semaphore lying around. sysvsem don't have the usual unix
Umm they have SEM_UNDO. Its a case of deeper magic
-
To unsubscribe from
On Fri, Nov 03, 2000 at 06:51:05AM -0800, David S. Miller wrote:
Are you saying that the original bug report may not actually be a
problem? Is ms-rss actually protected in _all_ of the right
places, but people got confused because of the syntactic sugar?
I don't know if all of
1 - 100 of 188 matches
Mail list logo
