I found a bug in the patches for kernel 2.4.4.
When i use 2.4.4 clean, with no patches
hde: IBM-DTLA-307020, ATA DISK drive
hde: 40188960 sectors (20577 MB) w/1916KiB Cache, CHS=39870/16/63,
UDMA(100)
then, using kernel 2.4.4 with ac11 patch...
hde: IBM-DTLA-307020, ATA DISK drive
hde:
On Mon, 21 May 2001, Jakob Østergaard wrote:
> On Sun, May 20, 2001 at 10:10:49PM -0400, Robert M. Love wrote:
> >
> > im not installing python2 from source just so i can run some new config
> > utility.
>
> python2 will be in rawhide when 2.5 development requires it, if I'm not much
> mistaken.
Ph. Marek writes:
> in fs/devfs/util.c is
> void __init devfs_make_root (const char *name)
> which is wrong as pivot_root allows changing the root-device in the runtime.
>
> I think it should be
> void __init devfs_make_root (const char *name)
> and get called by
> fs/super.c:
>
On Sun, 20 May 2001, Marcelo Tosatti wrote:
> On Sat, 19 May 2001, Mike Galbraith wrote:
>
> > @@ -1054,7 +1033,7 @@
> > if (!zone->size)
> > continue;
> >
> > - while (zone->free_pages < zone->pages_low) {
On 21 May 2001, Jes Sorensen wrote:
> John> Au contraire. It is very reasonable to have both python and
> John> python2 installed. Having two different gcc versions installed
> John> is a big pain in the arse.
>
> It's not unreasonable to have both installed, it's unreasonable to
> require
On Sun, 20 May 2001, Rik van Riel wrote:
> On Sun, 20 May 2001, Mike Galbraith wrote:
> > On 20 May 2001, Zlatko Calusic wrote:
>
> > > Also in all recent kernels, if the machine is swapping, swap cache
> > > grows without limits and is hard to recycle, but then again that is
> > > a known
On 20 May 2001, Robert M. Love wrote:
> I feel that there should *never ever* be a legit situation that the
> configuration tool does not allow. Not ever. Two reasons:
>
> First, I tend to trust the config tools (perhaps too much). If they
> tell me x implies y, or x implies not y, I will
On Sun, 20 May 2001, Eric S. Raymond wrote:
> In order to prevent that happening, I would like to have some recognized
> criterion for configuration cases that are so perverse that it is a
> net loss to accept the additional complexity of handling them within the
> configurator.
Simple: That
On Mon, 21 May 2001, Ingo Molnar wrote:
>
> On Sun, 20 May 2001, Alexander Viro wrote:
>
> > Linus, as much as I'd like to agree with you, you are hopeless
> > optimist. 90% of drivers contain code written by stupid gits.
>
> 90% of drivers contain code written by people who do driver
From: "Alexander Viro" <[EMAIL PROTECTED]>
> On Sun, 20 May 2001, Paul Fulghum wrote:
> > I'll be the first to admit there is some ugliness in my driver.
>
> So will anyone here regarding his or her code. Count me in, BTW.
>
> Could you reread the posting you are refering to?
Sorry if I
> derive MVME147_SCSI from MVME147 & SCSI
It seems that the preferred semantics would be:
default MVME147_SCSI from MVME147 & SCSI
That way the platform defines sane defaults, but no flexibility has been
taken away.
Presumably many of these defaulted options would also be ones that would
be
Mikulas Patocka wrote:
>If you are checking permissions on server, read/execute have no security
>meaning.
This seems a bit too strong. If I try to exec a file that has read
permission enabled but not execute permission, I'd like this to fail.
You can just imagine sysadmins who turn off exec
Did not get the word on change to video_register_device added parameter
nr something.
Garst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
On Mon, May 21, 2001 at 12:19:49AM +0200, Ingo Oeser wrote:
> AFAIK "const" is only a promise to the compiler, that we write
> this data ONCE and read only after this initial write. So the
> decision on the section is implementation defined.
No, the problem is not with which section, but what
On Sun, May 20, 2001 at 10:10:49PM -0400, Robert M. Love wrote:
> On 21 May 2001 02:29:17 +0200, Jes Sorensen wrote:
> > John> Au contraire. It is very reasonable to have both python and
> > John> python2 installed. Having two different gcc versions installed
> > John> is a big pain in the
Okay, so Jeff Garzik already knows about this - I told him last week -
but seeing as how the code has made it to a Linus pre-release without
a fix I thought I'd better post the breakage description to l-k!
The symptoms are:
In 2.4.5-pre4 (and 2.4.4-ac8 and above - note: I didn't try -ac7)
system
On 21 May 2001 02:29:17 +0200, Jes Sorensen wrote:
> John> Au contraire. It is very reasonable to have both python and
> John> python2 installed. Having two different gcc versions installed
> John> is a big pain in the arse.
>
> It's not unreasonable to have both installed, it's unreasonable
Ingo Molnar wrote:
>
> On Sat, 19 May 2001, Jacob Luna Lundberg wrote:
>
> > This is 2.4.4 with the aic7xxx driver version 6.1.13 dropped in.
>
> > Unable to handle kernel paging request at virtual address 78626970
>
> this appears to be some sort of DMA-corruption or other memory scribble
>
On Mon, May 21, 2001 at 02:29:17AM +0200, Jes Sorensen wrote:
> distributions). 18 months is more realistic for it to be deployed
> widely enough.
People who are going to be savvy enough to install a development 2.5.*
kernel that is defining a new configuration utility are going to be savvy
On Sun, May 20, 2001 at 06:03:44PM -0700, David S. Miller wrote:
> But for the time being, everyone assumes address zero is not valid and
> it shouldn't be too painful to reserve the first page of DMA space
> until we fix this issue.
Indeed, virtually all PCI systems have legacy PeeCee
The hardware: UP1000 Alpha, with ALI M1543C IDE. Fujitsu 2GB udma33
drive, I think. ATAPI UDMA CDROM.
The problem: 2.2.15 (as packaged with MDK 7.1 for Alpha) works fine.
2.4.current, both ac tree and linus tree, fail to work at all. I've
tried all combinations I can think of, for: with
On Sun, May 20, 2001 at 06:01:40PM -0700, David S. Miller wrote:
>
> Andrea Arcangeli writes:
> > > Well this is news to me. No drivers understand this.
> >
> > Yes, almost all drivers are buggy.
>
> No, the interface says that the DMA routines may not return failure.
The alpha returns a
On Sun, May 20, 2001 at 06:07:17PM -0700, David S. Miller wrote:
>
> Andrea Arcangeli writes:
> > > [..] Even sparc64's fancy
> > > iommu-based pci_map_single() always succeeds.
> >
> > Whatever sparc64 does to hide the driver bugs you can break it if you
> > pci_map 4G+1 bytes of phyical
Hi,
The following patch fixes ppc xconfig potential problem introduced in
2.4.5-pre4.
Andrzej
***
diff -uNr linux-2.4.5-pre4/arch/ppc/config.in linux-pre4/arch/ppc/config.in
--- linux-2.4.5-pre4/arch/ppc/config.in Mon May 21
David Woodhouse <[EMAIL PROTECTED]>:
> Let's not talk about CONFIG_AUNT_TILLIE any more, or change the existing
> behaviour of config options to make that the default, until we've settled
> the discussion about CML2.
What discussion is that? Unless Linus has changed his mind and I don't
know
Andrea Arcangeli writes:
> > [..] Even sparc64's fancy
> > iommu-based pci_map_single() always succeeds.
>
> Whatever sparc64 does to hide the driver bugs you can break it if you
> pci_map 4G+1 bytes of phyical memory.
Which is an utterly stupid thing to do.
Please construct a plausable
Em Sun, May 20, 2001 at 08:46:44PM +0100, Alan Cox escreveu:
> > So I have 2 questions:
> > 1) Does anyone know if Leonard Zubkoff is still around?
>
> Leonard was around at OLS last year and working at VA. Its possible he was
> laid off but I've heard nothing to suggest that so he's probably
Andrea Arcangeli writes:
> > Well this is news to me. No drivers understand this.
>
> Yes, almost all drivers are buggy.
No, the interface says that the DMA routines may not return failure.
If you want to change the DMA api to act some other way, then fine
please propose it, but do not
On Sun, 20 May 2001 22:16:11 +0200,
Franz Sirl <[EMAIL PROTECTED]> wrote:
>Yes, and gcc3 errors on these constructs, cause it cannot decide if the data
>should be put into a .data or .rodata section.
>Dunno if it's worth to create a __initconstdata/__initrodata though, but it
>would be easy
> "Eric" == Eric S Raymond <[EMAIL PROTECTED]> writes:
Eric> The first candidates I found were questions associated with
Eric> built-in SCSI and Ethernet on Macintoshes, on the Sun 3 and
Eric> Sun3x, and with built-in facilities on the MVME147 single-board
Eric> computer. So I wrote
On Sun, May 20, 2001 at 04:05:18PM +0400, Ivan Kokshaysky wrote:
> Ok. What do you think about reorg like this:
> basically leave the old code as is, and add
> if (is_pyxis)
> alpha_mv.mv_pci_tbi = cia_pci_tbi_try2;
> else
> tbia test
>
On Sun, 20 May 2001, Paul Fulghum wrote:
> I'll be the first to admit there is some ugliness in my driver.
So will anyone here regarding his or her code. Count me in, BTW.
Could you reread the posting you are refering to?
-
To unsubscribe from this list: send the line "unsubscribe
On Mon, 21 May 2001, Ingo Molnar wrote:
>
> On Sun, 20 May 2001, Alexander Viro wrote:
>
> > Linus, as much as I'd like to agree with you, you are hopeless
> > optimist. 90% of drivers contain code written by stupid gits.
>
> 90% of drivers contain code written by people who do driver
> "John" == John Cowan <[EMAIL PROTECTED]> writes:
John> Jes Sorensen wrote:
>> Telling them to install an updated gcc for kernel compilation is a
>> necessary evil, which can easily be done without disturbing the
>> rest of the system. Updating the system's python installation is
>> not a
>> 90% of drivers contain code written by stupid gits.
>
> From: "Alan Cox"
> I think thats a very arrogant and very mistaken view of the problem. 90%
> of the driver are written by people who are
>
> - Copying from other drivers
> - Using the existing API's to make their job easy
> - Working to
On Sun, 20 May 2001 11:47:38 -0400,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>Somebody failed to track a module name change.
>-obj-$(CONFIG_BBC_I2C) += bbc.o
>+obj-$(CONFIG_BBC_I2C) += bbc_i2c.o
bbc-objs := bbc_i2c.o bbc_envctrl.o
The module is bbc.o,
Linus Torvalds writes:
> If you add the page argument, why leave the old arguments lingering there
> at all? They only create confusion, and add no information.
You mean the `to' pointer argument, or the `vaddr' argument? The
`vaddr' argument isn't redundant, it's the user virtual address
On Sun, 20 May 2001, Alexander Viro wrote:
> Linus, as much as I'd like to agree with you, you are hopeless
> optimist. 90% of drivers contain code written by stupid gits.
90% of drivers contain code written by people who do driver development in
their spare time, with limited resources, most
On Mon, 21 May 2001, Matti Aarnio wrote:
> In some cases even the fast-paths carry FP/MMX code,
> but those are cases where the save/restore overhead
> becomes negligible for all of the other processing
> that is going on.
even in that case you must make sure you dont
Hi,
I am using Proxim Symphony Wireless LAN card on one of my systems with kernel
2.2.19. I may reinstall with a different Linux distro and upgrade to kernel 2.4.
The Proxim Symphony Wireless LAN site (http://www.komacke.com) has disappeared.
Does anyone know where I can find drivers for Linux
[EMAIL PROTECTED] said:
> Maybe it would be possible to separate "hard" dependencies like the
> current system has with the "soft" ones one needs for entry-level
> configtools.
Actually, the current system has both types. As well as the "hard"
dependencies, we also have stuff like
Hi
> I'm trying to impelemnt a lightweight network filesystem and ran into
> trouble implementing lookup, permissions and open.
>
> The protocol requires me to specify open mode in it's open command. The
> open mode has 4 bits: read, write, append and execute. But I can't tell
> execution from
I can't see anything immediately wrong with your code - make sure you're
compiling against the source for the kernel you're running, with the same
options enabled.
In general, though, you shouldn't be using any of the sleep_on() functions
if you care about the fact that you'll miss wakeup
Okay I think I've gotten it solved most of the way, we weren't calling
execve via the system call interface, so once I made it go via the system
call and I fill out pc, sp and psl registers in start_thread, it seems to
go further..
Thanks for all the help...
Dave.
On Sun, 20 May 2001, Kenn
On Sat, 19 May 2001, Mike Galbraith wrote:
> @@ -1054,7 +1033,7 @@
> if (!zone->size)
> continue;
>
> - while (zone->free_pages < zone->pages_low) {
> + while
On Sun, May 20, 2001 at 05:34:48PM -0400, Jeff Garzik wrote:
> This might be a very valid point...
>
> (let me know if the following test is flawed)
It is imho.
> > [jgarzik@rum tmp]$ cat > sectest.c
> > #include
> > #include
> > static const char version[] __initdata = "foo";
static
On Sun, May 20, 2001 at 05:24:48PM +0100, Dave Airlie wrote:
>
> I'm implementing start_thread for the VAX port and am wondering does
> start_thread have to return to load_elf_binary? I'm working on the init
> thread and what is happening is it is returning the whole way back to the
> execve
On Sun, May 20, 2001 at 09:51:04PM +0200, Geert Uytterhoeven wrote:
> Appendix: here's the list of affected source files:
>
> arch/arm/kernel/setup.c
Thanks for pointing it out.
--
Russell King ([EMAIL PROTECTED])The developer of ARM Linux
After man-pages-1.36 and kbd-1.06 today util-linux-2.11c.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Geert Uytterhoeven wrote:
>
> On Sun, 20 May 2001, Jeff Garzik wrote:
> > Geert Uytterhoeven wrote:
> > > Since a while include/linux/init.h contains the line
> > >
> > > * Also note, that this data cannot be "const".
> > >
> > > Why is this? Because const data will be put in a different
On Sun, 20 May 2001, Mike Galbraith wrote:
> On 20 May 2001, Zlatko Calusic wrote:
> > Also in all recent kernels, if the machine is swapping, swap cache
> > grows without limits and is hard to recycle, but then again that is
> > a known problem.
>
> This one bugs me. I do not see that and
On 20 May 2001, Robert M. Love wrote:
> hi,
>
> is there a sqrt function in the kernel?
no. read the FAQ.
> i tried finding/grepping around, and found some various arch-specific
> stuff for fpu emulation... is there a general sqrt function? is there a
In general questions like this are
On Sun, May 20, 2001 at 04:33:20PM -0400, Robert M. Love wrote:
> hi,
>
> is there a sqrt function in the kernel? any other math functions?
No. (Assuming FP math sqrt function is your interest.)
If you do scaled integers (fractions, with 2^n denominator),
you can do
On 20 May 2001 16:47:00 -0400, Eric S. Raymond wrote:
> In order to prevent that happening, I would like to have some recognized
> criterion for configuration cases that are so perverse that it is a
> net loss to accept the additional complexity of handling them within the
> configurator.
>
> A
On Sun, 20 May 2001, Mike Galbraith wrote:
> > Also in all recent kernels, if the machine is swapping, swap cache
> > grows without limits and is hard to recycle, but then again that is
> > a known problem.
>
> This one bugs me. I do not see that and can't understand why.
To throw away
On Sun, May 20, 2001 at 04:47:00PM -0400, Eric S. Raymond wrote:
> In order to prevent that happening, I would like to have some recognized
> criterion for configuration cases that are so perverse that it is a
> net loss to accept the additional complexity of handling them within the
>
[EMAIL PROTECTED] said:
> I'm nervous that if we go down this path we will end up with a
> thicket of modes and a combinatorial explosion in ruleset complexity,
> leading immediately to a user configuration experience that is more
> complex than necessary, and eventually to an unmaintainable
> the system with problem is using kernel 2.4.2 on an P200 with 64mb ram. It
> has about 20 users that use the box... (ftp, telnet, lynx, bitchx,...).
>
> the problem is when the parameter tcp_mem HIGH gets exeded after about a
day
> of use! Then the box is going from the net and its not
David Woodhouse <[EMAIL PROTECTED]>:
> I think you already have the mechanism required to answer this - in NOVICE
> mode you disallow the strange choices, in EXPERT mode you allow them.
That pushes the third button. I'm nervous that if we go down this path
we will end up with a thicket of
On Sun, 20 May 2001, Alan Cox wrote:
> > Linus, as much as I'd like to agree with you, you are hopeless optimist.
> > 90% of drivers contain code written by stupid gits.
^^^
>
> I think thats a very arrogant and very mistaken view of the problem. 90%
> of the driver are
hi,
is there a sqrt function in the kernel? any other math functions?
i tried finding/grepping around, and found some various arch-specific
stuff for fpu emulation... is there a general sqrt function? is there a
single file to look through with the various math functions?
thanks,
--
Robert
On Sun, May 20, 2001 at 07:33:15PM +0200, David Osojnik wrote:
> the system with problem is using kernel 2.4.2 on an P200 with 64mb ram. It
> has about 20 users that use the box... (ftp, telnet, lynx, bitchx,...).
>
> the problem is when the parameter tcp_mem HIGH gets exeded after about a day
On Sun, 20 May 2001, Jeff Garzik wrote:
> Geert Uytterhoeven wrote:
> > Since a while include/linux/init.h contains the line
> >
> > * Also note, that this data cannot be "const".
> >
> > Why is this? Because const data will be put in a different section?
>
> Causes a "section type
On Sunday 20 May 2001 21:51, Geert Uytterhoeven wrote:
> Since a while include/linux/init.h contains the line
>
> * Also note, that this data cannot be "const".
>
> Why is this? Because const data will be put in a different section?
Yes, and gcc3 errors on these constructs, cause it cannot
Jonathan Morton <[EMAIL PROTECTED]>:
> One caveat though - not all Macs have SCSI controllers, and not all that do
> even have one of the two standard ones.
I know. But these derivations are only for the old 68K macs, which don't
have PCI. Closed issue.
> >3. The MVME derivations are correct
Hy to all !
I am experiencing big problems using wait queues in a device driver
(module)
on kernel 2.4.3-20mdk (gcc version 2.96).
I dont know if this is the right place to ask for - but its my last hope...
The device driver i write is for a measuring device connected to parallel
port-
so i'm
> Linus, as much as I'd like to agree with you, you are hopeless optimist.
> 90% of drivers contain code written by stupid gits.
I think thats a very arrogant and very mistaken view of the problem. 90%
of the driver are written by people who are
- Copying from other drivers
spam goes to /dev/null wrote:
> i created a 10mb file called .enc2 with random data and ran "# losetup -e
> serpent -k 128 /dev/loop0 /mnt/hda7/.enc2"
> then i ran "# mke2fs /dev/loop0" and tried to "# mount /dev/loop0 /enc". but
> i get the following error messages when trying to mount:
>
> May
Geert Uytterhoeven wrote:
>
> Since a while include/linux/init.h contains the line
>
> * Also note, that this data cannot be "const".
>
> Why is this? Because const data will be put in a different section?
Causes a "section type conflict" build error, at least on x86.
> FWIW, many
The patch makes the driver use the dma mapping interface.
It compiles.
No adequate adapter for testing.
--- linux-2.4.4-ac11/drivers/net/fealnx.c Sat May 19 14:36:37 2001
+++ linux-2.4.4-ac11/drivers/net/fealnx.c Sun May 20 15:53:26 2001
@@ -46,6 +46,8 @@ static int
[EMAIL PROTECTED] said:
> Now, a good way to force the issue may be to just remove the "ioctl"
> function pointer from the file operations structure altogether. We
> don't have to force peopel to use "read/write" - we can just make it
> clear that ioctl's _have_ to be wrapped, and that the only
Richard Reynolds wrote:
>
> I would have never signed up for this list, or any other if it didn't give me at
> least a few hours worth of email bouncing neither myself, or usa.net is up
> 24/7/365, and i wouldn't expect that everyone has a dedicated email server, for
> almost any list. plus I
Since a while include/linux/init.h contains the line
* Also note, that this data cannot be "const".
Why is this? Because const data will be put in a different section?
However, quite some code defines const __init variables (see list below).
So what should be done now?
1. Remove const
> I'm confused. I've always wondered that before you suspend the state
> of a machine to disk, why we just don't throw away unnecessary data
> like anything not actively referenced.
swsusp does exactly that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
> So I have 2 questions:
> 1) Does anyone know if Leonard Zubkoff is still around?
Leonard was around at OLS last year and working at VA. Its possible he was
laid off but I've heard nothing to suggest that so he's probably just busy
or on holiday
> 2) Is anyone else looking after the BusLogic
> > printk("%s\n", version);
> >
> > Not quite as optimal but safer.
>
> I disagree. Don't work around an escape bug in a version string, fix
> it...
A % in a version string might be quite reasonable. You are asking to have
an accident by avoiding it. If you want to fight over 4
> > If it had been a manufacturer in most respectable areas of business they'd be
> > recalling and reissuing components, and paying for the end resllers to notify
> > each customer
>
> This is consumer hardware. Consumer products are optimized for a
> good buzzword count per $ ratio.
On Sun, 20 May 2001, Linus Torvalds wrote:
> No, but the point is, everybody _would_ consider it a bug if a
> low-level driver "write()" did anything but touched the explicit buffer.
>
> Code like that would not pass through anybody's yuck-o-meter. People would
> point fingers and say "That
Davem, check the last thing, please.
On Sun, 20 May 2001, Alexander Viro wrote:
>
> On Sun, 20 May 2001, Linus Torvalds wrote:
>
> > > How about moratorium on new ioctls in the meanwhile? Whatever we do in
> > > fs/ioctl.c, it _will_ take time.
> >
> > Ehh.. Telling people "don't do that"
On Sun, 20 May 2001, Alexander Viro wrote:
>
> On Sun, 20 May 2001, Matthew Wilcox wrote:
>
> > On Sun, May 20, 2001 at 03:11:53PM -0400, Alexander Viro wrote:
> > > Pheeew... Could you spell "about megabyte of stuff in ioctl.c"?
> >
> > No.
> >
> > $ ls -l arch/*/kernel/ioctl32*.c
> >
I would have never signed up for this list, or any other if it didn't give me at
least a few hours worth of email bouncing neither myself, or usa.net is up
24/7/365, and i wouldn't expect that everyone has a dedicated email server, for
almost any list. plus I have had many problems with the
On Sun, 20 May 2001, Linus Torvalds wrote:
> > How about moratorium on new ioctls in the meanwhile? Whatever we do in
> > fs/ioctl.c, it _will_ take time.
>
> Ehh.. Telling people "don't do that" simply doesn't work. Not if they can
> do it easily anyway. Things really don't get fixed unless
On Sun, 20 May 2001, Edgar Toernig wrote:
> IMHO any similar powerful (and versatile) interface will see the same
> problems. Enforcing a read/write like interface (and rejecting drivers
> that pass ptrs through this interface) may give you some knowledge about
> the kernel/userspace
On Sun, 20 May 2001, Alexander Viro wrote:
>
> Pheeew... Could you spell "about megabyte of stuff in ioctl.c"?
I agree. But it would certainly force people to think about this. And it
may turn out that a lot of it can be streamlined, and not that much ends
up being used very much.
It would
On Sun, 20 May 2001, Matthew Wilcox wrote:
> On Sun, May 20, 2001 at 03:11:53PM -0400, Alexander Viro wrote:
> > Pheeew... Could you spell "about megabyte of stuff in ioctl.c"?
>
> No.
>
> $ ls -l arch/*/kernel/ioctl32*.c
> -rw-r--r--1 willywilly 22479 Jan 24 16:59
On Sun, 20 May 2001, Jacob Luna Lundberg wrote:
> > > Unable to handle kernel paging request at virtual address 78626970
> > this appears to be some sort of DMA-corruption or other memory scribble
> > problem. hexa 78626970 is ASCII "pibx", which shows in the direction of
> > some sort of
On Sun, May 20, 2001 at 03:11:53PM -0400, Alexander Viro wrote:
> Pheeew... Could you spell "about megabyte of stuff in ioctl.c"?
No.
$ ls -l arch/*/kernel/ioctl32*.c
-rw-r--r--1 willywilly 22479 Jan 24 16:59 arch/mips64/kernel/ioctl32.c
-rw-r--r--1 willywilly 109475
Alexander Viro wrote:
>
> On Sun, 20 May 2001, Edgar Toernig wrote:
>
> > IMHO any scheme that requires a special name to perform ioctl like
> > functions will not work. Often you don't known the name of the
> > device you're talking to and then you're lost.
>
> ls -l /proc/self/fd/
Oh come
On Sun, 20 May 2001, Ingo Molnar wrote:
> > Unable to handle kernel paging request at virtual address 78626970
> this appears to be some sort of DMA-corruption or other memory scribble
> problem. hexa 78626970 is ASCII "pibx", which shows in the direction of
> some sort of disk-related DMA
On Sun, 20 May 2001, Linus Torvalds wrote:
> Now, a good way to force the issue may be to just remove the "ioctl"
> function pointer from the file operations structure altogether. We don't
> have to force peopel to use "read/write" - we can just make it clear that
> ioctl's _have_ to be
On Sun, 20 May 2001, Russell King wrote:
>
> On Sun, May 20, 2001 at 11:46:33AM -0700, Linus Torvalds wrote:
> > Nobody will expect the above to work, and everybody will agree that the
> > above is a BUG if the read() call will actually follow the pointer.
>
> I didn't say anything about
On Sun, May 20, 2001 at 06:28:24AM -0400, Mike A. Harris wrote:
> On Sun, 20 May 2001, Shawn Starr wrote:
> >My emails may bounce between 3AM -> 8AM Est time, @Home is doing some
> >fiber upgrades and i dont have a second MX server (as I am the
> >domain/dns/mail etc).
There is 3d+ some
On Sun, 20 May 2001, David Woodhouse wrote:
>
> If that had been done right the first time, you wouldn't have had to either.
> For that matter, it's often the case that if the ioctl had been done right
> the first time, nobody would have had to fix it up for any architecture.
The problem with
On Sun, May 20, 2001 at 11:46:33AM -0700, Linus Torvalds wrote:
> Nobody will expect the above to work, and everybody will agree that the
> above is a BUG if the read() call will actually follow the pointer.
I didn't say anything about read(). I said write(). Obviously it
wouldn't work for
On Sun, 20 May 2001, Russell King wrote:
>
> On Sat, May 19, 2001 at 08:26:20PM -0700, Linus Torvalds wrote:
> > You're missing the point.
>
> I don't think Richard is actually. I think Richard has hit a nail
> dead on its head.
>
> > It's ok to do "read()/write()" on structures.
>
> Ok, we
On Sun, 20 May 2001, Paul Mackerras wrote:
>
> The patch below adds a page * argument to copy_user_page and
> clear_user_page.
If you add the page argument, why leave the old arguments lingering there
at all? They only create confusion, and add no information.
Linus
-
To
Hi.
The following trivial patch against 2.4.4(-ac11) makes ps2esdi compile.
--- linux-244-ac10-clean/drivers/block/ps2esdi.cSat May 19 21:06:29 2001
+++ linux-244-ac10/drivers/block/ps2esdi.c Sun May 20 14:47:04 2001
@@ -953,10 +953,10 @@
break;
}
>1. The Mac derivations were half-right. The MAC_SCC one is good but Macs
>can have either of two different SCSI controllers. I fixed that with help
>from Ray Knight, who maintains the 68K Mac port.
If I understand the "philosophy" correctly, it is still possible to specify
additional cards
[EMAIL PROTECTED] said:
> I'm implementing start_thread for the VAX port and am wondering does
> start_thread have to return to load_elf_binary? I'm working on the
> init thread and what is happening is it is returning the whole way
> back to the execve caller .. which I know shouldn't
Hi Peter.
> I've trying to move some of my servers to 2.4.4 kernel from
> 2.2.x. Everything goes fine, notable perfomance increase
> occures, but the problem is I'm really often touch the following
> problem:
> __alloc_pages: 1-order allocation failed.
> __alloc_pages: 1-order allocation
1 - 100 of 347 matches
Mail list logo
