Hi Rik,
On Thu, 16 Nov 2000, Rik van Riel wrote:
> On 16 Nov 2000, Christoph Rohland wrote:
>> Also we have to make sure to derefence the swap entry if the
>> last reference is in the shm segmant table .
>
> Why is this?
Because you never get a page fault on the shm segmants. So you never
will
On Fri, Nov 17, 2000 at 12:30:46AM -0700, Erik Andersen wrote:
> On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote:
> > >
> > > - pre6:
> > > - Intel: start to add Pentium IV specific stuff (128-byte cacheline
> > > etc)
> > > - David Miller: search-and-destroy places
-BEGIN PGP SIGNED MESSAGE-
he flags what he considers 'critical fixes' with the level 1 tag
(something about them being level 1 problems or something like that)
David Lang
On Fri, 17 Nov 2000, Erik Andersen wrote:
> Date: Fri, 17 Nov 2000 00:30:46 -0700
> From: Erik Andersen <[EMAIL
Hello
I try to compile 2.4.0-test11-pre6, and recive error:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686-c -o dev.o
dev.c
dev.c: In function `run_sbin_hotplug':
dev.c:2736: `hotplug_path' undeclared
On Thu, 16 Nov 2000, Jacob Luna Lundberg wrote:
>
> I'm not (yet) a kernel guru, so just point and laugh if I'm wrong, but...
>
> On Thu, 16 Nov 2000, Dan Aloni wrote:
> > - if (!--de->count) {
> > + if (atomic_dec_and_test(>count)) {
>
> Doesn't this reverse the
On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote:
> >
> > - pre6:
> > - Intel: start to add Pentium IV specific stuff (128-byte cacheline
> > etc)
> > - David Miller: search-and-destroy places that forget to mark us
> > running after removing us from a
* fs_may_remount_ro() used the wrong check for skipping the
files being in the middle of final fput(). NULL ->f_dentry is
possible here (after all references to file are gone, etc.), NULL
->f_dentry->d_inode isn't. I.e. check in
file_list_lock();
for (p = sb->s_files.next;
Followup to: <[EMAIL PROTECTED]>
By author:Peter Samuelson <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
>
> [jesse]
> > 1. Your server closes all open directory file descriptors and chroots.
> > 2. Someone manages to run some exploit code in your process space which--
>
>
[jesse]
> 1. Your server closes all open directory file descriptors and chroots.
> 2. Someone manages to run some exploit code in your process space which--
mkdir("foo")
chroot("foo")
chdir("../../../../../../../../../..")
chroot(".")
mkdir proc
mount -t proc none proc
cd
-- Forwarded by Rajiv Majumdar/CAL/NOTES on 11/17/2000
11:00 AM ---
[EMAIL PROTECTED] on 11/17/2000 10:24:00 PM
To: [EMAIL PROTECTED]
cc: Rajiv Majumdar/CAL/NOTES, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: FW:
On Fri, 17 Nov 2000, Frank Davis wrote:
> Hello,
> I just try to compile 2.4.0-test11-pre6, and received the following error (make
>modules):
>
> inode.c:1054 conflicting types for 'new_inode'
> /usr/src/liunux/include/linux/fs.h:1153 previous declaration of 'new_inode'
My fault. Hell
* Arrgh. Hell knows how, but %s/new_inode/ntfs_&/g in fs/ntfs/inode.c
mentioned in the previous part didn't make it into the patch I've sent.
Mea maxima culpa. Fixed.
* More duplicated initializations removed:
* get_empty_inode() sets i_flags to 0. NFS and UDF did
Now that sendmail/load average problems have been nailed for 2.2.18>
2.4, the mailing lists are working. We apologize, but the server was
upgraded and during the upgrade, most folks addresses got zapped in the
var/lib/majordomo/lists directory, so folks who want to track Andre and
our work on
Neil Brown wrote:
>
> On Thursday November 16, [EMAIL PROTECTED] wrote:
> > FYI:
> >
> > gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes
>-O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
>-march=i686-c -o dev.o dev.c
> >
I'm not (yet) a kernel guru, so just point and laugh if I'm wrong, but...
On Thu, 16 Nov 2000, Dan Aloni wrote:
> - if (!--de->count) {
> + if (atomic_dec_and_test(>count)) {
Doesn't this reverse the sense of the test?
-Jacob
--
"My my, the cruelest lies are
Hello,
I just try to compile 2.4.0-test11-pre6, and received the following error (make
modules):
inode.c:1054 conflicting types for 'new_inode'
/usr/src/liunux/include/linux/fs.h:1153 previous declaration of 'new_inode'
make[2]: ***[inode.o]Error 1
make[2]: Leaving directory
[Jeff Garzik]
> MYSRC=/devel/linux-2.4
>
> tar xvfz linux-2.4.0-test11.tar.gz
> mv linux linux-vanilla
> diff -urN linux-vanilla $MYSRC > /tmp/patch
You should use an example where $MYSRC is a single directory level
(rather than absolute path) so people can use 'patch
sir,
i am getting some problem with graphics mode. my system is opening in text
mode only. upto yesterday it is ok. but now it is failing to open in
graphics mode. i am using startx, xinit and Xconfigurator all options. but
even it is showing errors. it is displaying something cannot set font
I noticed that for 2.4.0-testXX there was no help
for CONFIG_TOSHIBA, although there is for 2.2.17.
The following patch borrows the words for CONFIG_TOSHIBA
from the 2.2.17 Documentation/Configure.help.
I checked that the URL referenced below is still valid, and it is.
And CONFIG_TOSHIBA is
I have patches written to improve the accuracy of CPU measurement
(getrusage()) and virtual itimers. This lets the amount of CPU used
by a process be measured fairly accurately. The patches are on my web
page: http://members.home.com/minyard
This is if anyone is interested. I don't know if
From: "Ying Chen/Almaden/IBM" <[EMAIL PROTECTED]>
Date:Thu, 16 Nov 2000 19:02:25 -0800
You forgot about wakeup_bdflush(1) stuff.
What are you talking about, did you even check the
patch?
Your changes are already in there.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To
Hi all
I\'ve asked this question on a few other email list with no responce, so as a
last resort I\'m posting it here.
I\'m trying to get a system going which has two links to the internet. One has
class C range routed over it and the other will need to be Masq\'d.
I want to route traffic
On Thursday November 16, [EMAIL PROTECTED] wrote:
> FYI:
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes -O2
>-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
>-march=i686-c -o dev.o dev.c
> dev.c: In function
Linus,
You forgot about wakeup_bdflush(1) stuff.
Here is the patch again (against test10).
===
There are several places where schedule() is called after wakeup_bdflush(1)
is called. This is completely unnecessary, since
On Thu, Nov 16, 2000 at 08:40:29PM -0700, Jeff V. Merkey wrote:
> Petr,
>
> NCPFS in 2.2.18-pre21 is not returning volume size via df -h. I checked
> your code and found this comment:
>
> static int ncp_statfs(struct super_block *sb, struct statfs *buf, int bufsiz)
> {
> struct statfs
FYI:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686-c -o dev.o dev.c
dev.c: In function `run_sbin_hotplug':
dev.c:2736: `hotplug_path' undeclared (first use in
Jens Axboe wrote:
> Wouldn't it be more interesting to fix the reason the new error
> handling code dies with imm and ppa?
Yes it would... :o) I think I've got it here.
The new error handling code spinlocks the IRQ which cause the lowlevel
parport driver to choke. This patch unlocks, allows the
In message <[EMAIL PROTECTED]> you write
:
> I think I got something, icmp_error_track() increases the use count
> (calling ip_conntrack_find_get()) when it returns with no error (not NULL).
The reference count is now held by the skb.
Hope that helps,
Rusty.
--
Hacking time.
-
To unsubscribe
Petr,
NCPFS in 2.2.18-pre21 is not returning volume size via df -h. I checked
your code and found this comment:
static int ncp_statfs(struct super_block *sb, struct statfs *buf, int bufsiz)
{
struct statfs tmp;
/* We cannot say how much disk space is left on a mounted
On Thu, Nov 16, 2000 at 06:33:11PM -0800, Linus Torvalds wrote:
>
> The log-file says it all..
>
> Linus
>
> -
>
> - pre6:
> - Intel: start to add Pentium IV specific stuff (128-byte cacheline
> etc)
> - David Miller: search-and-destroy places that forget to
The log-file says it all..
Linus
-
- pre6:
- Intel: start to add Pentium IV specific stuff (128-byte cacheline
etc)
- David Miller: search-and-destroy places that forget to mark us
running after removing us from a wait-queue.
- me: NFS client
Alan and Tigran's comments folded in and Wiki-fied ;)
http://kernelbook.sourceforge.net:80/wiki/?PreparingPatches
This is not meant to replace the Documentation/... guide, only to
provide means for future public contributions. Consider it a
tentative preview, not a formal publication, and
In message <20001115154603.D4089@psuedomode> you write:
> I was DDoS'd today while away and came home to find the firewall unable to
> do anything network related (although my connection to irc was still
> working oddly). a quick dmesg showed the problem.
> ip_conntrack: maximum limit of 2048
This patch for 2.4.0-test11-pre5 allows the use of the FM radio tuner
on BT848 cards even if the driver is not compiled as a module.
What it does: it adds the boot command line parameter bt848_radio=,
which works exactly like the radio= parameter of the bttv module.
Note: on my system, gtuner
I am sure you knew this perfectly well already but just in case it is helpful:
the offending code is in:
drivers/ide/piix.c::piix_dmaproc [starts on line 402 in 2.4.0-test11-pre5]
It calls piix_config_drive_for_dma and only then calls ide_dmaproc.
It is ide_dmaproc that does the good/bad test
Then I need to fix that to prevent the bypass that should not happen.
On Fri, 17 Nov 2000, Anton Altaparmakov wrote:
> The drive was being added to the black lists fine it's just that I had PIIX
> tuning enabled which caused the good/bad dma tables check to be bypassed
> completely. - So
The drive was being added to the black lists fine it's just that I had PIIX
tuning enabled which caused the good/bad dma tables check to be bypassed
completely. - So disabling PIIX tuning made my PC boot fine.
Regards,
Anton
At 00:13 17/11/2000, Anton Altaparmakov wrote:
>Hello all,
>
>I
In message <[EMAIL PROTECTED]> you write:
> On 14 Nov 2000 11:42:42 -0800,
> "H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
> >Seriously, though, I don't see any reason modprobe shouldn't accept
> >funky filenames. There is a standard way to do that, which is to have
> >an argument consisting of
The BTTV driver 0.7.48 doesn't detect my old Hauppauge card anymore.
The problem seems to be that my card sets PCI_SUBSYSTEM_ID and
PCI_SUBSYSTEM_VENDOR_ID to zero (lspci output below).
In 2.4.0-test10-pre5, the card was correctly detected as a
"Hauppauge old". If I set btv->type to 2 in
> both 2.2.x and 2.4.x kernels can't read `real sky' CDs
Yes. 2.0.38 is OK. I just made a patch that seems to work.
Harald, could you try
ftp.xx.kernel.org/.../people/aeb/linux-2.4.0test9-isofs-patch
and report?
Linus, Alan - I made patches for 2.2 and 2.4 but want to
polish and check
Portable code must only use set_bit() on a long, otherwise Sparc64 and
mips64 break (and probably PPC64 in future).
Personally, I'd be much happier if set_bit(N,addr) were defined to
operate on the byte `(char *)addr + N/8': then we could use it on
`char', etc, as well (ie. set_le_bit renamed to
Hello all,
I have an ide hard drive that misbehaves when the option "enable DMA at
boot time" (2.4.x kernel) is selected (this is on a on board ide
controller). But on the other hand I have a Promise Ultra-ATA-100
controller with an IBM ATA-100 drive that, according to the menuconfig
On Thu, 16 Nov 2000, David Feuer wrote:
> At 06:10 PM 11/16/2000 -0500, you wrote:
> >Here's one more: you can't rename across the binding boundary. They _are_
> >mounts, so they avoid all that crap with loop creation on rename, etc.
> >Take a generic DAG and try to implement rename() analog
> > I do not believe so. I tend to think that detecting these broken models is a
>waste of kernel code (especially, if there's an effort to correct the problem).
>
> One idea the Dell folks suggested is walking the SMBIOS data table. That happens
> to be something I want to do as its the only
At 06:10 PM 11/16/2000 -0500, you wrote:
>Here's one more: you can't rename across the binding boundary. They _are_
>mounts, so they avoid all that crap with loop creation on rename, etc.
>Take a generic DAG and try to implement rename() analog on it. Have fun
>catching the cases that would make
Hi,
When I saw the mad16.c driver, I just couldn't resist.
There were 7 (seven) levels of nested ifs.
It looks like more cleaning can be done, but this patch is just
reorganising the code without any functionality change and makes the
questionable logic more readable.
Patch against latest
Hi Jeff,
I compared my personal hints list to yours.
Yours is much more complete and better.
Here are a few comments for you to consider (below).
Thanks,
~Randy_
|randy.dunlap_at_intel.com503-677-5408|
|NOTE: Any views presented here are mine
Followup to: <[EMAIL PROTECTED]>
By author:Vojtech Pavlik <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Anyway, this should be solvable by checking for clock change in the
> timer interrupt. This way we should be able to detect when the clock
> went weird with a 10 ms accuracy. And
On 16 Nov 2000, H. Peter Anvin wrote:
[hardlinks on directories]
> I don't believe it's inherently impossible in Linux anymore. In fact,
Yes, it is. bindings are asymmetrical. And that's the reason why they
work while links to directories do not.
> vfsbinds provide a lot of the same kind
> Please note that 2.91.66 WILL NOT correctly build any bit of 2.4 (or
> probably 2.2) on i386 that uses the kernel version of strstr, because of a
> register allocation bug. This currently affects the DEPCA driver, but very
> few other things.
>
> 2.95.2 is OK in this instance and elsewhere for
Sorry for the broken references - I read l-k through Kernel Traffic.
> At one point someone asked what the recommended compiler was for all the
> various kernel versions, and Peter Samuelson [*] listed:
>
> 2.91.66 aka egcs 1.1.2. It has been officially blessed for 2.4 and has
> been given an
On Thu, 16 Nov 2000, jesse wrote:
> But the problem is because you can call chroot when you're already chrooted.
It's a non-problem. chroot()ing again may also be used to de-escalate
privileges, and if you want to prevent breaking out of a chroot, drop
root privileges, since chroot is a
Followup to: <[EMAIL PROTECTED]>
By author:David Feuer <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> . and foo/. are also links, not directories... the directories themselves
> are filesystem internal objects, and not discussed by the standard. I
> didn't know that linux
On Thu, 16 Nov 2000, Alan Cox wrote:
> > The Unofficial Linus HOWTO
>
> 'Care And Operation Of Your Linus Torvalds'
>
>
> > mv linux linux-vanilla
> > diff -urN linux-vanilla $MYSRC > /tmp/patch
>
> Include Tigrans recommended exclude list and info
Alan Cox is very
Followup to: <[EMAIL PROTECTED]>
By author:Keith Owens <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On Thu, 16 Nov 2000 22:21:52 +0100,
> Xavier Bestel <[EMAIL PROTECTED]> wrote:
> >as modprobe (insmod) args parsing seems POSIX compliant, we should put a
> >"--" before
> >what
As part of the Linux Scalability Effort (lse) project at
SourceForge, we have published a call for participation
in the area of Scheduler Scalability:
http://lse.sourceforge.net/CFP/ScaleSchedProj-1.html
If this is an area of interest to you, please join the
lse-tech mailing list.
> The Unofficial Linus HOWTO
'Care And Operation Of Your Linus Torvalds'
> mv linux linux-vanilla
> diff -urN linux-vanilla $MYSRC > /tmp/patch
Include Tigrans recommended exclude list and info
> code. A MIME attachment also takes Linus a bit more time to process,
On Thu, 16 Nov 2000 22:21:52 +0100,
Xavier Bestel <[EMAIL PROTECTED]> wrote:
>as modprobe (insmod) args parsing seems POSIX compliant, we should put a
>"--" before
>what should be interpreted only as a textual argument, not as an option.
>This is a lot safer: whatever is passed, modprobe will
Tobias Ringstrom wrote:
> On Wed, 15 Nov 2000, Jeff Garzik wrote:
> > Tobias Ringstrom wrote:
> > > I have updated the dmfe.c network driver for 2.4.0-test by adding proper
> > > locking (I hope), and also made transmission much efficient.
> > Would you mind creating a separate patch that -just-
On Wed, 15 Nov 2000, Jeff Garzik wrote:
> Tobias Ringstrom wrote:
> >
> > I have updated the dmfe.c network driver for 2.4.0-test by adding proper
> > locking (I hope), and also made transmission much efficient.
> >
> > I would appreciate any feedback from people using this driver, to confirm
> >Then dev_load is being called the wrong way. In older kernels we explicitly
> >only did a dev_load with user passed names providing suser() was true.
>
> ping6 -I module_name. ping6 is setuid, it passes the interface name to
> the kernel while it holds root privileges, suser() == true. It
> I do not believe so. I tend to think that detecting these broken models is a waste
>of kernel code (especially, if there's an effort to correct the problem).
One idea the Dell folks suggested is walking the SMBIOS data table. That happens
to be something I want to do as its the only good way
On Thu, Nov 16, 2000 at 01:26:36PM -0800, [EMAIL PROTECTED] wrote:
>
> > Ted, is this true? It would be wonderfull to be able to use i82365 without
> > need for pcmcia_cs...
>
> > I think in-kernel pcmcia crashing even on simple things *is* critical bug.
It wasn't a critical bug, in the sense
> It's simply not good enough to close all directory file descriptors before chrooting.
>
> If calling chroot once you're already in a chroot jail was disallowed, it would stop
> this attack.
I think the problem here is that some people have the idea that chroot is
some kind of magical
I am seeing a kernel panic on 2.2.14. It looks like 2.2.16 also has the
same problem.
Details:
I have been able to reproduce a kernel panic several times with kdb
compiled in and some added printk debug messages and I have now
pinpointed the problem. The panic occurs when the following call is
I'd like to put the following document into the kernel tree as
linux/Documentation/SubmittingPatches, and would like to get comments
on it.
I've likely left out a lot in Section 2... additions welcome.
I don't want to get too domain-specific in section 2, but I would
like to cover as many
On Thu, 16 Nov 2000, Linus Torvalds wrote:
> On Thu, 16 Nov 2000, Dan Aloni wrote:
> >
> > Makes procfs use an atomic use count for dir entries, to avoid using
> > the Big kernel lock. Axboe says it looks ok.
>
> There's a race there. Look at what happens if de_put() races with
>
On 16 Nov 2000, Christoph Rohland wrote:
> Oh, I missed one point: we need to handle the swapout of
> nonattached pages: in shm you can detach the last user and the
> segment with content is still around. So we have to scan the shm
> objects themselves also. Should We could do this in the same
>
Oh, I missed one point: we need to handle the swapout of nonattached
pages: in shm you can detach the last user and the segment with
content is still around. So we have to scan the shm objects themselves
also. Should We could do this in the same loop as we scan the mm's?
Also we have to make
Date: Sat, 1 Jan 2000 02:54:52 +
From: Pavel Machek <[EMAIL PROTECTED]>
Cc: David Woodhouse <[EMAIL PROTECTED]>, David Hinds <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
> It's purposefully not on Ted's
Hi,
as modprobe (insmod) args parsing seems POSIX compliant, we should put a
"--" before
what should be interpreted only as a textual argument, not as an option.
This is a lot safer: whatever is passed, modprobe will take it as a module
name.
--- linux-2.4.0-test10/kernel/kmod.cTue Sep 26
John D. Kim wrote:
> Well, there will be a great number of these laptops sold, not just through
> dell, but other brands that buy from compal. But most of them will be
> running Windows, and Windows seem to work fine with it. So these
[snip]
FWIW, Windows uses ACPI on these machines, not APM.
Frederic LESPEZ <[EMAIL PROTECTED]> writes:
> I think the problem is due to a bad PCI detection but i let you judge.
> Here is a description of the problem :
> I'm under X (Xfree 4.0.1).
> I switch to a VT (virtual terminal).
> I load my sound module (modprobe emu10k1).
could you try with the
At 07:51 PM 11/16/2000 +0100, you wrote:
>Now I see your point : by "." or "foo/." you mean the directory itself,
>while "foo" or "foo/" refer to the link to the directory, and they are
>obviously different objects... at least since hard links on directories
>were introduced. Fine.
. and foo/.
On Thu, 16 Nov 2000, Dan Aloni wrote:
>
> Makes procfs use an atomic use count for dir entries, to avoid using
> the Big kernel lock. Axboe says it looks ok.
There's a race there. Look at what happens if de_put() races with
remove_proc_entry(): we'd do free_proc_entry() twice. Not good.
(against test11-pre5)
Makes procfs use an atomic use count for dir entries, to avoid using
the Big kernel lock. Axboe says it looks ok.
--- linux/fs/proc/inode.c Wed Jun 21 17:25:17 2000
+++ linux/fs/proc/inode.c Thu Nov 16 19:09:28 2000
@@ -25,7 +25,7 @@
struct proc_dir_entry *
Hi,
Please bear with me, it's my first bug report and my first post to this
list.
Bear with my english too.
[1.] One line summary of the problem:
Bad PCI detection of a sound card
[2.] Full description of the problem/report:
I think the problem is due to a bad PCI detection but i let you
On Thu, 16 Nov 2000, Pavel Machek wrote:
> > > Because I set up a diskless Linux-workstation, I want to swap
> > > over NFS. For this purpose I found only patches for "older"
> > > Linux-versions (2.0, 2.1, 2.2?).
> >
> > > Does anyone know wheter there are patches for 2.4 or does anyone
> > >
Hi,
This comment is written in head of reschedule_idle, is it really
correct?
--
/*
* This is ugly, but reschedule_idle() is very timing-critical.
* We enter with the runqueue spinlock held, but we might end
* up unlocking it early, so the caller must not unlock the
Hi!
> > Cool. Linus, please could you apply this patch. If the fact that i82365
> > and tcic are broken in 2.4 isn't on Ted's critical list, then I think it
> > probably ought to have been - and this should fix it.
>
> It's purposefully not on Ted's critical list, the official line is "use
>
Hi!
> > Because I set up a diskless Linux-workstation, I want to swap
> > over NFS. For this purpose I found only patches for "older"
> > Linux-versions (2.0, 2.1, 2.2?).
>
> > Does anyone know wheter there are patches for 2.4 or does anyone
> > know another solution for this problem?
>
> 1.
On Thu, 16 Nov 2000, Rik van Riel wrote:
> On Thu, 16 Nov 2000, Szabolcs Szakacsits wrote:
> [snip exploit that really shouldn't take Linux down]
I don't really consider it as an exploit. It's a kind of workload
that's optimized for fast testing simulating many busy user daemons
(e.g.
On Thu, 16 Nov 2000 16:04:23 + (GMT),
Alan Cox <[EMAIL PROTECTED]> wrote:
>> request_module has the same effect as running suid. dev_load() can
>> take the interface name and pass it to modprobe unchanged and modprobe
>> does not verify its input, it trusts root/kernel.
>
>Then dev_load is
Hi.
Changes in the kernel has made the patch below necessary for sm.h:
--- linux-240-t11-pre5-clean/drivers/net/hamradio/soundmodem/sm.h Wed Aug 18
20:38:50 1999
+++ linux/drivers/net/hamradio/soundmodem/sm.h Thu Nov 16 20:33:17 2000
@@ -299,7 +299,7 @@
#ifdef __i386__
-#define
Hi.
Recent changes in the kernel has made the patch below necessary:
--- linux-240-t11-pre5-clean/drivers/net/hamradio/baycom_epp.c Sat Nov 4 23:27:07
2000
+++ linux/drivers/net/hamradio/baycom_epp.c Thu Nov 16 20:27:22 2000
@@ -812,10 +812,10 @@
/*
Hi!
This error ocurrs when "named" is executed. It exists since
2.4.0-test10preX or so.
I'm using RedHat 7.0 and my ethernet card is a "Kingston EtheRx KNE20
Plug and Play ISA Adapter". I'm unable to access the Internet because
the ethernet card doesn't work :-(
Bye!
--
D. Juan Piernas
> Alan Cox said once upon a time (Thu, 16 Nov 2000):
>
> > > I just got a Sceptre 6950 (also known as a Dell 5000e), I just installed
> > > Red Hat 7.0 on it, and got an APM related oops at boot.
> >
> > Yep. This is not a Linux problem
>
> The kernel works around/ignores/disables other broken
On Thu, Nov 16, 2000 at 11:52:49AM -0800, jesse wrote:
> On Thu, Nov 16, 2000 at 05:16:18PM +0100, Andrea Arcangeli wrote:
> > On Thu, Nov 16, 2000 at 03:07:04PM +0100, Matthias Andree wrote:
> > > It shows a program that saves the cwd -- open(".",...) in an open file,
> > > then chroots [..]
> >
On Thu, 16 Nov 2000, Alan Cox wrote:
> > The kernel works around/ignores/disables other broken hardware or broken
> > features of otherwise working hardware with black lists. There will be
> > many *many* of these laptops sold.
> And I hope many many of these people demand BIOS upgrades or send
On Thu, Nov 16, 2000 at 05:16:18PM +0100, Andrea Arcangeli wrote:
> On Thu, Nov 16, 2000 at 03:07:04PM +0100, Matthias Andree wrote:
> > It shows a program that saves the cwd -- open(".",...) in an open file,
> > then chroots [..]
>
> This is known behaviour (I know Alan knows about it too),
Andi Kleen <[EMAIL PROTECTED]> writes:
> [This is quite a bizarre discussion, but I'll answer anyways. I am not exactly
> sure what your point is]
Let me step aside a second and explain where I'm coming from. As a spin
off of the work of the linuxBIOS project I have implemented a system
call
Werner Almesberger <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
> > There are a couple of differences.
> > But the big one is I'm trying to do it right.
>
> So why do you need a file-based interface then ? ;-)
When possible it is nice to set as much policy as possible,
without
On Thu, 16 Nov 2000, Nishant Rao wrote:
>Date: Thu, 16 Nov 2000 11:55:24 -0600 (CST)
>From: Nishant Rao <[EMAIL PROTECTED]>
>To: Andi Kleen <[EMAIL PROTECTED]>
>Cc: [EMAIL PROTECTED]
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Subject: Re: Setting IP Options in the IP-Header
>
>Well, while what
Hi Rik,
On Thu, 16 Nov 2000, Rik van Riel wrote:
> On 16 Nov 2000, Christoph Rohland wrote:
>> So in shm_swap_out I check if the page is already in the swap
>> cache. If not I put the page into it and note the swap entry in
>> the shadow pte of shm. Right?
>
> Exactly. And I'll change
-
Red Hat, Inc. Security Advisory
Synopsis: Updated modutils fixing local root security bug available
Advisory ID: RHSA-2000:108-02
Issue date:2000-11-16
Updated on:2000-11-16
Hi,
as modprobe (insmod) seems to have POSIX args handling, we should perhaps add "--"
to the modprobe cmdline, in order to stop further args processing, and to avoid
mixing a textual argument with an option.
BTW, it should perhaps be generalized.
Xav
--- linux-2.4-test10/kernel/kmod.c
Howdy,
I have a couple of Sun sparcstation 2's (sun4c architectire) that reliably
fail in kmem_cache_alloc() whenever their kernel+initrd (net)boot image is
larger than about 2MB.
Each system has 48MB of RAM. Here's some relevant boot output
(printk() isn't actually working at this point, so
On Thu, 16 Nov 2000, Jean-Marc Saffroy wrote:
> Now I see your point : by "." or "foo/." you mean the directory itself,
> while "foo" or "foo/" refer to the link to the directory, and they are
> obviously different objects... at least since hard links on directories
> were introduced. Fine.
Hello!
> > It means that test for CAP_SYS_MODULE is illegal, moving pure policy
> > issue to improper place.
>
> Definitely not so
>
> What matters is whether the user is requesting a module or the kernel is
> choosing to load a module. In the former case where the user can influence the
>
On Thu, 16 Nov 2000, Alexander Viro wrote:
> > This is a point I don't understand here : do you mean that they are
> > confused if they can rmdir "." but not if they can rmdir their cwd
> > differently ? What's the difference ?
>
> rmdir() is _not_ "kill the directory identified by name and
1 - 100 of 388 matches
Mail list logo
