Same here. While it's a nice script and all, I personally want the
copyright and associated contact information in a clear and easy-to-find
place.
In other words, if you get Linus to patch the kernel to do this, then I'm
just going to try to get him to patch it back.
Matt
On Wed, Feb 14, 2001
Any debugging tips would be greatly appreciated.
When I cold boot my machine with a 3c575 and a Belkin
BusPort Mobile inserted in the Cardbus slots, I get
the following in my kernel log:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Yenta IRQ list 0698, PCI irq11
Socket
On Tue, 13 Feb 2001, Tim Waugh wrote:
> Here's a patch that fixes a bug that can cause PCI driver list
> corruption. If parport_pc's init_module fails after it calls
> pci_register_driver, cleanup_module isn't called and so it's still
> registered when it gets unloaded.
> ---
On Wed, 14 Feb 2001, Russell King wrote:
> Rick Hohensee writes:
> > ...
> > ## drop copyright notices to the bottoms of C files in current dir and
> > # subs.
>
> Please don't run this on any files maintained by myself.
Rick Hohensee writes:
> ...
> ## drop copyright notices to the bottoms of C files in current dir and
> # subs.
Please don't run this on any files maintained by myself. I want the
copyright notices to be prominently
hmmm this is my chipset:
Which motherboard do you have?
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton
I have a box w/ the following controllers:
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
I
Under 2.4.1-ac11 I'm getting errors like:
Feb 14 02:10:09 rhino kernel: Unused swap offset entry in swap_count 004dda00
Feb 14 02:10:09 rhino kernel: VM: Bad swap entry 004dda00
over and over. The system has 512M real and 1G swap allocated. This
is occuring at:
Mem:512492K total,
*
Hi, linux-kernel
What if Yahoo Paid You ? Now a reality !!!
World's first completely commissionable Portal just released.
Get paid as thousands search, email, or use any of our services.
14 months and 1.5 million dollars invested in the
On February 14, 2001 06:15 am, Mike Galbraith wrote:
> On Mon, 12 Feb 2001, C. D. Thompson-Walsh wrote:
> > [This sortof follows the format of the report form in REPORTING-BUGS]
> > 1. I've found a consistent set of circumstances which will hang 2.4.x
> > kernels on my system.
> >
> > 2. If the
On Wed, 14 Feb 2001, Willy Tarreau wrote:
> I think that most of us using modems begin to experience a little pain in
> downloading latest Alan's patches since they're becoming to be really big (and
> interesting).
>
> Since I have an occasionnal access to a system equipped with a good line, I
>
Hi all,
I think that most of us using modems begin to experience a little pain in
downloading latest Alan's patches since they're becoming to be really big (and
interesting).
Since I have an occasionnal access to a system equipped with a good line, I
began to make incremental patches for these
...
## drop copyright notices to the bottoms of C files in current dir and
# subs.
# /*
# CopYriGHt Guess Who 2001All reserves righted.
# */
grep -ilr "copyright" . > tempdropcopyrights
for f in
On Wed, Feb 14, 2001 at 12:27:10AM +1100, Andrew Morton wrote:
>
> It's getting very lonely testing this stuff. It would be useful if
> someone else could help out - at least running the bw_tcp tests. It's
> pretty simple:
>
> bw_tcp -s ; bw_tcp 0
OK, here's my bw_tcp results on a K6-2
On Tue, 13 Feb 2001, Zink, Dan wrote:
> Does it make sense to try and keep up with the latest and greatest in
> chipsets
> when there is a hardware independent way of doing things? You may be able
> to
> get information on current chipsets, but every time something changes, the
> kernel may be
On Mon, 12 Feb 2001, C. D. Thompson-Walsh wrote:
> [This sortof follows the format of the report form in REPORTING-BUGS]
> 1. I've found a consistent set of circumstances which will hang 2.4.x kernels
> on my system.
>
> 2. If the system is put under load to the point where it swaps heavily
>
> I was wondering why video drivers are not part of the kernel like every
> other piece of hardware. I would think if video drivers were part of the
> kernel and had a nice API for X or any other windowing system, would not
> only improve performance but would allow competing windowing systems
On Tue, 13 Feb 2001, Louis Garcia wrote:
> I was wondering why video drivers are not part of the kernel like every
> other piece of hardware.
See linux/drivers/video and linux/drivers/char/drm in kernel 2.4.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe
What is the status of "dloose udp" in 2.4.x? From my reading in a few list
archives it seems to have been some sort of a hack, yet it is needed for
games such as Asheron's Call to be played behind a firewall.
In 2.2.18 the code implementing this seems to be in net/ipv4/ip_masq.c
and was
Martin,
It looks like the numbers we picked for our respective IOCTLs conflict.
I think I can change mine to the next higher since your patch seems to
have been around longer. What is the general way to deal with these
conflicts?
--
Michael
On 13 Feb 2001, Martin K. Petersen wrote:
> >
On Wed, 14 Feb 2001, Manfred Spraul wrote:
> I have one additional user space only idea:
> have you tried raw-io? bind a raw device to the partition, IIRC raw-io
> is always in 512 byte units.
That has been tried. No, it does not work. :-) Using Scsi-Generic is the
only way so far found, but
On 12 Feb 2001, Jes Sorensen wrote:
> > "Donald" == Donald Becker <[EMAIL PROTECTED]> writes:
>
> Donald> On 9 Feb 2001, Jes Sorensen wrote:
> >> The ia64 kernel has gotten mis aligned load support, but it's slow
> >> as a dog so we really want to copy the packet every time anyway
> >> when
On Tue, 13 Feb 2001, Jaswinder Singh wrote:
> >
> > Can you point me to a cramfs generation procedure? (never used
> > cramfs.. know where the docs are, but could use a small time warp)
> >
>
> make ramdisk as you normally do and then compress it by gzip .
Ok, it's not a cramfs. If you
Hi
Well, it may not be a bug, but it sure is bugging me - i have been on this
for more than a week. Well, here goes;
Why is it that my DMA performance under the kernel 2.4.x is worse than the
one under 2.2? I have attached the stats below the mail- information and test
results under both
On Tue, 13 Feb 2001, Louis Garcia wrote:
> I was wondering why video drivers are not part of the kernel like every
> other piece of hardware. I would think if video drivers were part of the
> kernel and had a nice API for X or any other windowing system, would not
> only improve performance
Get rid of the special case in drivers/acpi/Makefile. mkdep now uses
the same -I options in the same order as the compiler. Against 2.4.1ac12.
Change from take 1 - make is too dumb to realise that /path/name/file.h
is the same as file.h when current directory is /path/name, so do not
use the
Get rid of the special case in drivers/acpi/Makefile. mkdep now uses
the same -I options in the same order as the compiler. Against 2.4.2-pre3.
Please jump up and down on this patch before I send it to Linus.
Change from take 1 - make is too dumb to realise that /path/name/file.h
is the same
I was wondering why video drivers are not part of the kernel like every
other piece of hardware. I would think if video drivers were part of the
kernel and had a nice API for X or any other windowing system, would not
only improve performance but would allow competing windowing systems
On Mon, Feb 12, 2001 at 02:33:17PM -0800, David S. Miller wrote:
> You have to add a few bits to arch/alpha/kernel/traps.c
> I could be wrong though...
Only to make the oops look pretty. Something like
die_if_kernel((type == 1 ? "Kernel Bug" : "Instruction fault"),
Alan Cox wrote:
> Ok we need to handle that case a bit more intelligently so those flushes dont
> get into other ports code paths.
Possibly at fs/buffer.c:end_buffer_io_async?
We need to flush the cache when I/O was READ or READA. Is there any
way for end_buffer_io_async to distinguish
On Tue, 13 Feb 2001 12:29:16 -0800, Ion Badulescu <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Feb 2001 07:06:44 -0600 (CST), Jeff Garzik
><[EMAIL PROTECTED]> wrote:
>
>> On 12 Feb 2001, Jes Sorensen wrote:
>>> In fact one has to look out for this and disable the feature in some
>>> cases. On the
Available at http://people.redhat.com/~sopwith/fidmour-linux.c is a driver
for the touch screen used on the Cassiopia Fiva MPC-501 pen computer. It
is a rather Bad Hack (seeing as it was built rather blindly to mimic the
behaviour of the Windows driver, and has IRQ/port hardcoded in), but it
On 12 Feb 2001, Jes Sorensen wrote:
> Ion> Yes, but I'd rather let people turn off the always-copy behavior
> Ion> by simply changing rx_copybreak. The unused code is not really
> Ion> that much of a deal, it's only a few lines.
>
> However, it is in the hot path code where it hurts the most.
> > While we can read and write to this sector in the kernel
> > partition code, we have
> > no way for userspace to update this partition block.
>
> Are you sure?
I'm not sure, but when I asked about this in January, I suggested having an
IOCTL that get/set
> "Andries" == Andries Brouwer <[EMAIL PROTECTED]> writes:
Andries> Anyway, an ioctl just to read the last sector is too silly.
Andries> An ioctl to change the blocksize is more reasonable.
I actually sent you a patch implementing this some time ago, remember?
We need it for XFS...
Patch
On Tue, 13 Feb 2001 22:10:27 +0100,
Yann Droneaud <[EMAIL PROTECTED]> wrote:
>Modprobe don't use alloca() correctly, then glibc failed. (stack corruption ?)
>This mail is sent to glibc, gcc and modutils maintainers.
Thanks, modutils bug, not a glibc problem. Against modutils 2.4.2.
Index:
On Tue, 13 Feb 2001 [EMAIL PROTECTED] wrote:
> SMP machine, 2x P3/700 on an Abit VP6.
> Never any trouble with the earlier 2.2.19pre's.
>
> a strace shows the hang to be in the delete_module("hisax") call.
I got another report of the same problem already. I'll try to sort it out
tomorrow.
Hello kernel-hackers,
I found a problem with kernel 2.4, that makes the kernel crash at
bootup, for example when using the UMC8672 VLB IDE controller driver.
The problem is in kernel/resource.c. In line 229 some memory for
handling new io-regions is kmalloc()ed. This crashes the computer
before
Michael E Brown wrote:
>
> >
> > Anyway, an ioctl just to read the last sector is too silly.
> > An ioctl to change the blocksize is more reasonable.
>
> That may be better, I don't know. That's why this is an RFC. Are there any
> possible races with that method? It seems to me that you might
ok, for those who didn't ignore :) trying to correct a misconfigured
MTA that made vger barf.
-
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
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686
-malign-functions=4-c -o init/main.o init/main.c
/usr/src/linux/include/asm/hw_irq.h: In function `x86_do_profile':
In file included from
On
Linux version 2.2.18
(gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release))
i got
Unable to handle kernel paging request at virtual address 74723e0a
current->tss.cr3 = 0353d000, %cr3 = 0353d000
*pde =
Oops:
CPU:0
EIP:0010:[]
EFLAGS: 00010816
eax:
Hi Tigran,
> PS. This only happens on this Dell latitude CPx (notice lost shift in
> Latitude?) H450GT.
I have a Dell Latitude CPx as well and I keep losing caps lock
keypresses. I'm running a 2.2.18 kernel. It's very annoying since I
have control mapped to caps lock.
I suspected that my
> " " == stergaard writes:
> What happens is that one machine will finish compiling, and
> another machine will immediately thereafter do a "touch
> some_output.o". This "touch" sometimes fails with a stale
> handle message.
Does the appended patch change anything?
Russell King wrote:
> Unless someone else (Rik/DaveM) says otherwise, it is my understanding
> that any IO for page P will only ever be a write to disk. Therefore,
> when you get a copy of the page from the swap cache, the physical memory
> for that page is the same as it was when the
From [EMAIL PROTECTED] Wed Feb 14 00:37:25 2001
> Look at the addpart utility in the util-linux package.
> It will allow you to add a partition disjoint from
> previously existing partitions.
> And since a partition can start on an odd sector,
> this should allow you to
Linus,
Here's a patch that fixes a bug that can cause PCI driver list
corruption. If parport_pc's init_module fails after it calls
pci_register_driver, cleanup_module isn't called and so it's still
registered when it gets unloaded.
Tim.
*/
2001-01-13 Tim Waugh <[EMAIL PROTECTED]>
*
> sorry. intel piii, with an adaptec AHA-294X Ultra2 scsi adapter. the
> disk in question is a 9gb IBM disk Model: DNES-309170W Rev: SA30. is
> this what you need? do you need more?
Thanks. Added to my collection of data, doesnt tally with other corruption
reports (other aic7xxx reports with the
On Tue, Feb 13, 2001 at 11:31:50PM +, Alan Cox wrote:
> > The NFS clients are getting
> > "Stale NFS handle"
> > messages every once in a while which will make a "touch somefile.o"
> > fail.
>
> If they have the previous .o handle cached and it was removed on another
> client thats quite
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
2.4.1-ac12
o Make tmpfs use link counts of 2 on directories (Christoph Rohland)
o Update Documentation/sound/Introductions(Wade Hampton)
o Fix bug in new tlb shootdown code (Ben LaHaise)
o
Alan Cox <[EMAIL PROTECTED]> writes:
> > i came in today to find the computer completely locked up. after
> > rebooting and waiting for about an hour for fsck to finish i found the
> > following errors in the system log:
>
> What hardware. I can see its some kind of scsi setup but what
Hi Andries!
On Tue, 13 Feb 2001 [EMAIL PROTECTED] wrote:
> > The block device uses 1K blocksize, and will prevent userspace from
> > seeing the odd-block at the end of the disk, if the disk is odd-size.
> >
> > IA-64 architecture defines a new partitioning scheme where there is a
> > backup
2.4.1-ac11 creates repeatedly the following error messages on my box:
kernel: VM: killing process crond (or any other process)
kernel: VM: Bad swap entry e200(variable addresses)
for example in intervals of about 5 to 10 seconds. This is on a notebook, AMD
K6-433, 64megs RAM, VIA
> i came in today to find the computer completely locked up. after
> rebooting and waiting for about an hour for fsck to finish i found the
> following errors in the system log:
What hardware. I can see its some kind of scsi setup but what interfaces ?
-
To unsubscribe from this list: send the
Excellent - this solved my problems. I stress tested the loopback device
with a big copy and it seemed to work. I also made losetup use open64:
[root@crush mount]# diff lomount.c lomount.c~
230c230
< if ((ffd = open64 (file, mode)) < 0) {
---
> if ((ffd = open (file, mode)) < 0) {
i came in today to find the computer completely locked up. after
rebooting and waiting for about an hour for fsck to finish i found the
following errors in the system log:
Feb 13 06:25:18 caliban kernel: EXT2-fs error (device sd(8,3)): ext2_readdir: bad
entry in directory #11: rec_len %% 4 != 0
> The NFS clients are getting
> "Stale NFS handle"
> messages every once in a while which will make a "touch somefile.o"
> fail.
If they have the previous .o handle cached and it was removed on another
client thats quite reasonable behaviour. NFS isnt coherent
> It's quite annoying and I
Hi !
I'm running a compilation cluster with various machines now
on 2.4.1 all mounting the same home filesystem over NFS from
the central NFS server.
All machines are 2.4.1 using NFSv3, some SMP some UP.
NFS server is a dual running an SMP kernel
The NFS clients are getting
"Stale NFS
On Tue, Feb 13, 2001 at 09:13:10PM +0100, Maciej W. Rozycki wrote:
> There is also an additional debugging/statistics counter provided in
> /proc/cpuinfo that counts interrupts which got delivered with its trigger
> mode mismatched. Check it out to find if you get any misdelivered
> interrupts
On Tue, 13 Feb 2001, Jeremy Jackson wrote:
> Next, gcc doesn't generate any code which would be placed in the
> stack, nor does it generate any calls/jumps to the stack area.
Unfortunately, you can't count on this. Objective C, for one, requires an
executable stack.
While there have been
S! Do not nudge sleeping penguin. Here is blow-by-blow of last incident:
http://kt.linuxcare.com/kernel-traffic/kt20001002_87.epl#1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
> locally over the loopback interface. This does not work without adding a
> bogus route statement to get the kernel to hand up the packets from
> loopback to my waiting application.
The multicast ABI includes the ability to toggle loopback of multicast
datagrams. Use the socket options instead
> 2.4.1-ac10 works fine (I had it up 24 hours before, and am again running
> it).
>
> Shortly after boot on 2.4.1-ac11, I get a ration of these:
> kernel: Unused swap offset entry in swap_count 0015fb04
Yep there is a small bug in the tlb shootdown fixes. Ben has fixed that. I'll
put up an
On Tue, 13 Feb 2001 21:22:26 + (GMT)
James Sutherland <[EMAIL PROTECTED]> wrote:
> On Tue, 13 Feb 2001, Jeremy Jackson wrote:
>
> (Long description of how to create a non-executable stack on x86)
>
> ISTR there is a patch which does this for Linux, though??
See:
In developing multicast applications, I would like to be able to test
locally over the loopback interface. This does not work without adding a
bogus route statement to get the kernel to hand up the packets from
loopback to my waiting application.
This route statement is not necessary with
[EMAIL PROTECTED] said:
> I'm wondering about the possibility of re-examining the idea of a
> kernel debugger option distributed with 2.4.
First off, I'd like to say that I'm highly sympathetic to this, assuming that
a kernel debugger doesn't change the kernel's behavior.
However,
> I'm
Andrey Panin wrote:
>
> Hi Brian.
>
> I'm sorry, patch itself was not attached in previous post :(
>
Yes, this does fix that part of the problem. There is still the matter
of the class code being wrong but I have ideas on how to fix that.
--
Philip R. Auld writes:
> Since deja was gobbled by google it's hard to do a good search of
> this list. Can anyone take the time to help me understand the reason
> for this choice? This seems to me to be backwards. When a device is
> unmounted there should be no cached information.
Try the
> The block device uses 1K blocksize, and will prevent userspace from
> seeing the odd-block at the end of the disk, if the disk is odd-size.
>
> IA-64 architecture defines a new partitioning scheme where there is a
> backup of the partition table header in the last sector of the disk. While
> That can be a problem for fiber channel devices. I saw some issues with
> invalidate_buffers and page caching discussed in 2.4 space. Any reasons
> come to mind why I shouldn't call invalidate on the the way down instead
> (or in addition)?
The I/O completed a few seconds later anyway when
Alan Cox wrote:
>
> > does not do anything to invalidate the buffers associated with the
> > unmounted device. We then rely on disk change detection on a
> > subsequent mount to prevent us from seeing the old super_block.
>
> 2.2 yes, 2.4 no
That can be a problem for fiber channel devices. I
** Reply to message from Miles Lane <[EMAIL PROTECTED]> on 13 Feb 2001
14:18:43 -0800
> The reason I asked about inclusion is that printing is one of the areas
> that Linux seems to struggle in terms of usability and I thought perhaps
> it would make sense to modular print drivers in the kernel
> does not do anything to invalidate the buffers associated with the
> unmounted device. We then rely on disk change detection on a
> subsequent mount to prevent us from seeing the old super_block.
2.2 yes, 2.4 no
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hello,
It appears that the umount path in the 2.2 series kernels
does not do anything to invalidate the buffers associated with the
unmounted device. We then rely on disk change detection on a
subsequent mount to prevent us from seeing the old super_block.
Since deja was gobbled by
Version 1.9 of my x86 performance-monitoring counters driver is
now available at http://www.csd.uu.se/~mikpe/linux/perfctr/.
Summary:
Version 1.9, 2001-02-13
- Fixed compilation problems for 2.2 and SMP kernels.
[Caused by the kernel not passing "-nostdinc" to gcc, and
RedHat 7.0 including
"Maciej W. Rozycki" wrote:
>
> Hi,
>
> After performing various tests I came to the following workaround for
> APIC lockups which people observe under IRQ load, mostly for networking
> stuff. I believe the test should work in all cases as it basically
> implements a manual replacement for EOI
Whoops.
The reason I asked about inclusion is that printing is one of the areas
that Linux seems to struggle in terms of usability and I thought perhaps
it would make sense to modular print drivers in the kernel tree. Since
the OMNI driver is ghostscript-based, including it in the kernel is
I'm wondering about the possibility of re-examining the idea of a kernel debugger
option distributed with 2.4.
I'm thinking that it could be a great teaching tool to break and examine structures,
variables, process states, as well as an aid to people who may not have a grasp
of the entire
test
-
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/
> Yes, actually it is... So I'm wrong then, it's not the same problem.
A rebuild of the binaries in question should fix it.
Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Maybe I'm missing your point, but why would it go into the kernel tree ?
This is all stuff that gets done in userland under Linux.
The Omni drivers plugin with Ghostscript and generate output appropriate to
the printer. There's no kernel relevance here.
Tim
On Tue, Feb 13, 2001 at 01:42:27PM
Sorry for all the fuss, I've been reliably informed, I put my foot in my
own mouth...
It was my net-tools package from Debian -(. I missed the fact I upgraded
some packages same day I upgraded my kernel.
I'll drop off the list again now. Sorry for the bother.
-
To unsubscribe from this list:
Miles Lane ([EMAIL PROTECTED]) said:
> http://oss.software.ibm.com/developer/opensource/linux/projects/omni/
Considering it's a ghostscript driver, I severely doubt it. :)
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Mon, Feb 12, 2001 at 11:09:39PM -0600, Matt Stegman wrote:
> Is there any kernel patch that would allow Linux to properly recognize,
> and execute gzipped executables?
What's wrong with using gzexe?
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL
http://oss.software.ibm.com/developer/opensource/linux/projects/omni/
-
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
I'm starting to work on an Intel i815 board.
I take this occasion to make a few updates
to the PCI device database, so it will be easier
to identify the whole hardware...
I changed the base, according what Intel says
in the datasheets for 82815 Chipset
and 82801BA Chip.
Here's the patch:
---
For the other list readers with problems:
I used patch 2.4.2-pre2 (not pre3)
plus axboe's loop-4 patch (in the people directory).
[EMAIL PROTECTED]:/pub/linux/kernel/people/axboe/patches/2.4.2-pre1
It solves most problems here.
-
To unsubscribe from this list: send the line "unsubscribe
Hi,
I found a strange bug with modprobe/glibc
I supposed this is a bad interaction between gcc alloca(), glibc and modprobe.
Modprobe don't use alloca() correctly, then glibc failed. (stack corruption ?)
This need more investigation.
This mail is sent to glibc, gcc and modutils maintainers.
>SMP machine, 2x P3/700 on an Abit VP6.
>Never any trouble with the earlier 2.2.19pre's.
>
>a strace shows the hang to be in the delete_module("hisax") call.
>
>I'm having trouble with the sysrq-key, but I hope this is enough since
>there were some changes w.r.t. modules/locking etc. in pre10.
>
On Tue, 13 Feb 2001, Jeremy Jackson wrote:
(Long description of how to create a non-executable stack on x86)
I'm afraid you just reinvented the wheel. The idea has been around for a
long time, and it was OK as a quick hack to stop existing exploits
working, but it's possible to modify a buffer
> It's Linux, after all, so 2 minutes after creating this email
> 2.2.19pre11's announcement was here. I just tested it, and it has the
> same problem.
Yep. Right now Im still working through the merges with Kai and I suspect
the merge when completed may not fix your bug, but that it'll get
Gordon Sadler wrote:
>
> I have some further info here.
> I performed strace on ifup -a and ifdown -a.
>
> They aren't more than 4Kb each, but I'll cut and paste what appear to be
> most relevant:
>
> ifup.strace:
> fork() = 17974
> wait4(17974, [WIFEXITED(s)
> which are marked
> supervisor-only (is this right?), and definitely don't contain user
> code.
x86 its a fair description. However someone has taken the same theory,
including handling the exceptions and the x86 segment tricks needed to make
it kind of fly. Its not a perfect cure but it
Greetings. This is my first post on linux-kernel, I hope this is
appropriate.
The recent CERT IN-2001-01 's massive repercussions and CA-2001-02's
re-releasing
old material in an attempt to coerce admins to update their OS, has led
me to think about
buffer overrun exploits. I have gained a
[EMAIL PROTECTED] (Kai Henningsen) writes:
>[EMAIL PROTECTED] (Henning P. Schmiedehausen) wrote on 12.02.01 in
><968mjv$l9t$[EMAIL PROTECTED]>:
>> [EMAIL PROTECTED] (Jan Gyselinck) writes:
>>
>> >There's not really something wrong with MX's pointing to CNAME's. It's
>> >just that some
SMP machine, 2x P3/700 on an Abit VP6.
Never any trouble with the earlier 2.2.19pre's.
a strace shows the hang to be in the delete_module("hisax") call.
I'm having trouble with the sysrq-key, but I hope this is enough since
there were some changes w.r.t. modules/locking etc. in pre10.
Good
Dear Mike ,
- Original Message -
From: "Mike Galbraith" <[EMAIL PROTECTED]>
To: "Jaswinder Singh" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 13, 2001 11:56 AM
Subject: Re: Problem with Ramdisk in linux-2.4.1
> On Tue, 13 Feb 2001, Jaswinder Singh wrote:
>
> >
"Mike A. Harris" <[EMAIL PROTECTED]> wrote:
>What is right:
>
>1) not putting the thing in the subject from the list side
>2) If an end user wants it in the subject, they can set up a mail
>filter to PUT it in the subject.
>
>:0 fwh
>* ^Sender:.*owner-linux-kernel
>| sed -e 's/^Subject:
On Tue, 13 Feb 2001 12:09:32 + (GMT), Michèl Alexandre Salim
<[EMAIL PROTECTED]> wrote:
> Currently running the XFree 4.0.2 from RH 7.0.90 (7.1
> beta, Fisher) on top of my RH 7 + Ximian system and
> when using aviplay it doesn't use any acceleration
> features at all, consequently choppy
> I have some further info here.
> I performed strace on ifup -a and ifdown -a.
Unfortunately you traced the script execution and nothing more useful so
I cant tell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
1 - 100 of 444 matches
Mail list logo
