he screen doesn't just go black. Probally the majority of
Matrox owners have multisync monitors, but I'm stuck with an old monosync,
and it looses sync when trying to return to a VESA text mode.
I don't use the matroxfb driver so this patch wouldn't help me, and is
also why I say XF
e problem with the
returning to VESA text modes from XFree 4.0 anytime I use the hallib, with
2.2 and 2.4 kernels. If I compile an X server without the hallib it's
fine (G450 users don't have that option, and I like my dual head).
If X changes the mode upon starting it should put it
be able to use a nice 132 character wide terminal
again. And I'm getting addicted to dual head in X, might be fun on the
console too.
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "you look like you are wearing a tuxedo." The second pen
d a lot of these sort of errors. I've already nailed a
few.
Cheers
Chris
On Fri, 13 Apr 2001, Dawson Engler wrote:
>
> We're looking at making a set of security checkers. Does anyone have
> suggestions for good things to go after in addition to the usual
> copy_*_user and
lons. Is the
acpi=no-idle work around the perminate fix?
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "you look like you are wearing a tuxedo." The second penguin
said, "I might be..." --David Lynch, Twin Peak
ce can any
exterior documentation be gleaned. Those of us who don't speak C would
really appreciate it.
Thanks In Advance.
Chris Kloiber
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info a
On Wed, 18 Apr 2001, David Schleef wrote:
> On Tue, Apr 17, 2001 at 09:39:15PM -0700, Dawson Engler wrote:
> > Hi All,
> >
> > at the suggestion of Chris ([EMAIL PROTECTED]) I wrote a simple
> > checker to warn when the length parameter to copy_*_user was (1) an
>
tempted into userspace. The
source is a kernel object which is not 2Gb large! So, we read off the end
of some kernel object, and there is often something very interesting after
it ;-)
For a good real-world example, please see my Bugtraq post regarding
sysctl():
http://www.securityfocus.com/archive
h
>> Erreur de segmentation ( SEGFAULT )
>> >> -and then the partition freeze .Any attempt to read/write on it leads to
Hmmm, are you sure there aren't any reiserfs messages on screen or in the
log?
-chris
-
To unsubscribe from this list: send the line "unsubscribe l
soon.
Anyway, this patch should fix 2.4.x, please apply:
-chris
--- linux/fs/reiserfs/journal.c.1 Tue Apr 17 09:36:36 2001
+++ linux/fs/reiserfs/journal.c Tue Apr 17 09:37:50 2001
@@ -2052,7 +2052,7 @@
sleep_on(&(SB_JOURNAL(p_s_sb)->j_join_wait)) ;
}
}
-lock_jo
call, mostly because I
didn't want to copy/maintain that hunk of code in reiserfs.
Testing has been light, I'll beat on it more this evening.
patch against 2.4.3-ac7.
-chris
diff -Nru a/fs/attr.c b/fs/attr.c
--- a/fs/attr.c Wed Apr 18 18:33:44 2001
+++ b/fs/attr.c Wed Apr 18 18:
Hi guys,
The reiserfs commit thread needs to daemonize. This patch
was actually from Andi Kleen eons ago (but blame me if
it breaks). Please apply.
Against 2.4.3:
--- linux/fs/reiserfs/journal.c Thu Apr 19 14:02:56 2001
+++ linux/fs/reiserfs/journal.c Thu Apr 19 18:11:57 2001
@@ -1814,16 +1
_from_fh(struct super_block *, __u32 *fh, int size) ;
iget the inode or parent directory inode based on data in the array.
Default ops are provided, the other filesystems should work the
same as before. Anyway, please take a look.
-chris
# This is a BitKeeper generated patch for the following pro
On Monday, February 12, 2001 11:42:38 PM +0300 Hans Reiser
<[EMAIL PROTECTED]> wrote:
>> Chris,
>>
>> Do you know if the people reporting the corruption with reiserfs on
>> 2.4 were using IDE drives with PIO mode and IDE multicount turned on?
>>
>&
After the updates to the opl3sa2 driver (2.4.2-pre3?) my card isn't being
detected anymore. Are there further updates to come, or do I need to
change the settings? The driver is being loaded as a module with the
following in /etc/modules.conf:
alias sound-slot-0 opl3sa2
options sound dmabuf=1
without them, you get this:
opl3sa2: io, mss_io, irq, dma, and dma2 must be set
Thanks for your help!
CF
On Tue, 13 Feb 2001, Jérôme Augé wrote:
> Chris Funderburg wrote:
> > following in /etc/modules.conf:
> >
> > alias sound-slot-0 opl3sa2
> > options sound d
On Tuesday, February 13, 2001 01:39:02 AM +0300 Hans Reiser
<[EMAIL PROTECTED]> wrote:
> Chris, your quoting is very confusing above. but I get your very
> interesting remark (thanks for noticing) that the nulls are specific to
> crashes on 2.2, and therefor could be due to t
On Mon, 12 Feb 2001, Scott Murray wrote:
Thanks!
The isapnp=0 fixed it. I don't actually have an isapnp.conf file.
On my next compile I'll just disable the ISA Pnp driver.
I don't actually need it, but it's something that I've never bothered to
turn off. :)
CF
>
is -ETIMEDOUT used? ...
TIA,
Chris
-
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://vger.kernel.org/lkml/
s as to what was going on? My only theory is that
something is screwy with the card or the drivers, but I have no idea why it
would run fine for almost 6 months then suddenly start causing problems.
I eagerly await your opinions.
Chris
-
To unsubscribe from this list: send the line "unsubscrib
Chris Friesen wrote:
> The kicker is that the NIC with the MAC address in question happened to be in my
> G4 box running linux (yellowdog, 2.2.17 kernel). It was a D-Link 530TX NIC, if
> it matters. The linux box was not configured as a DHCP server or client, and
> both interface
why people see null bytes.
If anyone wants more details, drop a line to me or the reiserfs
list ;-) This patch against 2.4.1 (will work on any 2.4.1ac or
2.4.2pre as well) should fix it, please try it on your
non-production machines, we are still running it through tests
here.
-chris
--- linux/fs
On Friday, February 16, 2001 05:01:39 PM +0100 Xuan Baldauf
<[EMAIL PROTECTED]> wrote:
>
>
> Chris Mason wrote:
>
>> Hello everyone,
>>
>> I think Alexander Zarochentcev and I have finally figured out
>> cause for null bytes in small reiserf
Repeat the write() - send another 1Mb.
--> BUG!! The call blocks indefinitely instead of returning with EAGAIN
after 5s.
I hope this is detailled enough. I'm trying to gain access to a FreeBSD
box to compare results..
Cheers
Chris
-
To unsubscribe from this list: send the line &quo
Alexey,
Damn you are quick! :) Testing immediately
Cheers
Chris
On Sat, 17 Feb 2001 [EMAIL PROTECTED] wrote:
> Hello!
>
> > Unfortunately, it seems to be very buggy. Here are two buggy scenarios.
>
>
> --- ../vger3-010210/linux/net/ipv4/tcp.c Sat Feb 10 23:16:51
.
- Set 5 seconds SO_SNDTIMEO on the connected socket
- Do a sendfile() from a big file down the connected socket. Make sure the
size is big (e.g. 1Mb) so the call blocks.
--> BUG!! The call blocks indefinitely rather than being interrupted after
5 seconds.
Cheers
Chris
On Sat, 17 Feb 2001 [EM
oduced binary.
>
Where in the libsample.so file are the differences (what byte offset?).
Are they restricted to a given range, or do they vary randomly?
> These problems occur on:
>
> 2.4.1
> 2.4.2-pre4
> 2.4.2-pre4 with Chris Mason's 'reiserfs fix for null bytes in
Hi,
By the way - I tested SO_RCVLOWAT, another 2.4 addition. Good news this
time - seems to work fine.
Cheers
Chris
-
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
not very robust, as it
> does not detect garbled input files). As said, running objdump on the
> corrupted (reiserfs compiled) library also produces errors.
Great, that will help narrow things down. Please run the elf-dynstr-gc
program under strace, on top of both the ext2 and reiserfs tree
If your bug is *really*
odd, I might ask a few different ways, just to make sure you give the same
answer every time ;-)
-chris
-
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.k
which I
can't account for.
Cheers
Chris
-
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/
an a timeout error), and the loop goes around
again.
> If transmission of any page never takes more than SO_SNDTIMEO it never
> times out.
Which is good, because SO_SNDTIMEO is an inactivity monitor.
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
s fixed. I think the FreeBSD
behaviour is definitely correct and we want it on Linux.
Cheers
Chris
--- filemap.c.old Sun Feb 18 23:35:06 2001
+++ filemap.c Mon Feb 19 00:13:38 2001
@@ -1062,7 +1062,7 @@
for (;;) {
struct page *page, **hash;
- unsign
On Mon, 19 Feb 2001, Chris Evans wrote:
> > BTW, if you have enough fast network, you probably can observe
> > that sendfile() is even not interrupted by signals. 8) But this
> > is possible to fix at least. BTW the same fix will repair SO_*TIMEO
> > partially, i.e.
wrong on that and one other thing. NFS doesnt work
> without extra patches and big endian boxes dont work with reiserfs
> currently
>
> Chris - would it be worth sending me a patch that notes the NFS thing in
> Configure.help and includes the patch url ?
Yes, it would. I'd rath
On Tuesday, February 20, 2001 11:40:24 AM +1100 Neil Brown
<[EMAIL PROTECTED]> wrote:
>
> When reiserfs came along, it abused this, and re-interpreted the
> opaque datum to contain information for recalling (locating) an
> inode - if read_inode2 was defined. I think this is wrong.
>
I s
t be a useful thing to export to userspace.
Cheers
Chris
-
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/
ffee break and come back to it, there's still
>> no evidence that you banged on the keyboard.
>
>
> Wild shot in the darkI'd lay odds that you had about 6-7 Megs free in
> your buffers/cache line, yes?
>
David, have any of Rik's patches helped here
ing the
userspace NFS server with reiserfs:
ftp.suse.com/pub/people/ak/nfs
-chris
-
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/
inds of deadlocks should have been long since
fixed, so there is probably a larger problem.
Running reiserfsck --replay-journal will replay the journal. This happens
on every mount, so I'm really not sure how it could have fixed things ;-)
The --check option is readonly, and if there was
h tea: 3m58s
The percentage increase just gets bigger as you create more and more files.
That doesn't mean this is a real world case, but it is what the hash was
designed for.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
e in 32Mb, were the caching not out of balance.
Cheers
Chris
-
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/
port back if switching to 2.95.2 or
egcs fixed the oops.
Anyway, which compiler did you use to compile the kernel?
-chris
-
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.ker
On Friday, February 23, 2001 10:18:56 PM +0100 Erik Mouw
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I am running linux-2.4.2-pre4 with Chris Mason's tailconversion bug fix
> applied, but I still have problems with null bytes in files. I wrote a
> little test prog
est program does not close the fd by the way, so some of the
errors were from that (but not all).
So, there must be somewhere else that we are screwing up the tail
conversion, I'll see what I can find.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
eing set right. It is more than possible that I've screwed up
something there, and the code thinks a page is valid when it really isn't.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More ma
unformatted node
after a direct->indirect conversion. This code only gets called when the
page/buffer wasn't already up to date, which is why you see it more when
there is less ram.
Fix will be out shortly
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-k
been copied. This was the big bug, it was zeroing previously
copied bytes.
Any testing on non-production machines would be appreciated,
I'll forward to Linus/Alan once I've gotten more feedback.
-chris
diff -ur diff/linux/fs/reiserfs/inode.c linux/fs/reiserfs/inode.c
--- diff/linux/fs
ew_file_size + [one block], and
then truncate that block off the end of the file, leaving nothing but the
hole. I'll never admit to suggesting it though.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
mprove the vm by careful profiling, tweaking and benching, not by
throwing random patches in that seem cool in theory.
Cheers
Chris
-
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:/
filesystems need to grab the bkl on their own for fsync now:
-chris
--- linux/Documentation/filesystems/Locking.1 Fri Mar 2 11:20:18 2001
+++ linux/Documentation/filesystems/Locking Fri Mar 2 11:21:10 2001
@@ -229,7 +229,7 @@
open: maybe (see below)
flush: yes
ecific fsync
op needs to be called. But, you should not need to call file_fsync in the
XFS fsync call (check out ext2's)
For why ide is beating scsi in this benchmark...make sure tagged queueing
is on (or increase the queue length?). For the xlog.c test posted, I would
expect scsi to get fast
ll restrict
their scans to a list of dirty buffers for that specific file. Only
file_fsync goes through all the dirty buffers on the device, and the ext2
fsync path never calls file_fsync.
Or am I missing something?
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
*/
- next = idle_task(this_cpu);
- c = -1000;
if (prev->state == TASK_RUNNING)
goto still_running;
+ next = idle_task(this_cpu);
+ c = -1000;
still_running_back:
list_for_each(tmp, &runqueue_head) {
--END-OF-PATC
g
SCSI bus is being reset for host 0 channel 0.
SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2802
[valid=0] Info fld=0x0, Current sd08:02: sense key Illegal Request
Additional sense indicates Invalid command operation code
scsidisk I/O error: dev 08:02, sector 163868
(scsi
On Thursday, January 04, 2001 10:48:13 AM +0100 Christoph Rohland
<[EMAIL PROTECTED]> wrote:
> Chris Mason <[EMAIL PROTECTED]> writes:
>> Just noticed the filemap_fdatasync code doesn't check the return value
>> from writepage. Linus, would you take a patch tha
(page) ;
UnlockPage(page) ;
}
And then, in filemap_fdatawait:
list_del(&page->list) ;
if (PageDirty(page))
list_add(&page->list, &mapping->dirty_pages) ;
else
list_add(&page->list, &mapping->clean_pages) ;
-chris
-
To unsubscribe from this list: send the line &qu
Hi guys,
Looks like the prerelease, and at least test13 don't fsync the device when
someone does an unmount on /
mount -o remount works, just unmounting the root misses the fsync.
This patch works for me:
-chris
--- linux/fs/super.c.1 Thu Jan 4 13:38:55 2001
+++ linux/fs/super.cTh
On Thursday, January 04, 2001 01:58:47 PM -0500 Alexander Viro
<[EMAIL PROTECTED]> wrote:
> On Thu, 4 Jan 2001, Chris Mason wrote:
>
>> Looks like the prerelease, and at least test13 don't fsync the device
>> when someone does an unmount on /
>>
>> mo
k with
the new kernel.
Log the super before balancing to avoid warning messages about
logging an unprepared buffer.
Clears the dirty bit before sending buffers to submit_bh
in reiserfs_writepage.
Please send any bug reports to the reiserfs list.
-chris
diff -urN linux-3.6.23/fs/buffer.c linux/
two of you ajourn this debate to alt.flame
Better still stop _theorizing_ and start _measuring_
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Friday, January 05, 2001 02:04:08 PM +0100 Claas Langbehn
<[EMAIL PROTECTED]> wrote:
> On Thu, Jan 04, 2001 at 04:52:49PM -0500, Chris Mason wrote:
>> This patch is meant to be applied on top of the reiserfs
>> 3.6.23 patch to get everything working in the new prerel
Here's the latest version of the patch, against 2.4.0. The
biggest open issues are what to do with bdflush, since
page_launder could do everything bdflush does. And, how to
deal with writepage funcs that return 1 for fsync_inode_buffers.
-chris
diff -urN linux.2.4.0/fs/buffer.c lin
On Fri, 5 Jan 2001, Chris Mason wrote:
> > Could someone create one single patch for the 2.4.0 ?
> >
> I put all the code into CVS, and Yura is making the official patch now.
Since 2.4.0 final should fix a few i/o performance issues (particuarly
under heavy write loads), a qu
ioned in the MAINTAINERS file for this
ISA PNP card, and I have received no response from the linux-sound
mailing list.
Is there anybody out there?
Cheers,
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Pleas
Alan Cox wrote:
>
> > 1) The amount of video memory is being incorrectly reported my the VESA call
> > used in arch/i386/video.S (INT 10h AX=4f00h). My Dell Inspiron 3200 (NeoMagic
> > video) returns that it has 31 64k blocks of video memory, instead of the
> > correct 32. This means that vesa
16992 0 (autoclean) [sscape]
mpu401 18928 0 (autoclean) [sscape]
sound 56976 0 (autoclean) [sscape ad1848 mpu401]
soundcore 3952 5 (autoclean) [sscape sound]
So although sscape can load mpu401 and ad1848, it mustn't unload them? The mixer c
On Friday, January 05, 2001 02:54:53 PM -0200 Rik van Riel
<[EMAIL PROTECTED]> wrote:
> On Fri, 5 Jan 2001, Chris Evans wrote:
>> On Fri, 5 Jan 2001, Chris Mason wrote:
>>
>> > > Could someone create one single patch for the 2.4.0 ?
>> > >
>>
On Friday, January 05, 2001 01:43:07 PM -0200 Marcelo Tosatti
<[EMAIL PROTECTED]> wrote:
>
> On Fri, 5 Jan 2001, Chris Mason wrote:
>
>>
>> Here's the latest version of the patch, against 2.4.0. The
>> biggest open issues are what to do with b
On Friday, January 05, 2001 01:43:07 PM -0200 Marcelo Tosatti
<[EMAIL PROTECTED]> wrote:
>
> On Fri, 5 Jan 2001, Chris Mason wrote:
>
>>
>> Here's the latest version of the patch, against 2.4.0. The
>> biggest open issues are what to do with b
s (not some async daemon), and the writing only starts when we are
over the hard dirty limit.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Hi,
I recently posted a patch for the coprocessor device in the 2.4.0 sound drivers. Well,
it appears that I missed the synth device in the mpu401.c file and so here is an
updated version.
Cheers,
Chris
diff -urN -X linux-2.4.0/dontdiff linux-vanilla/drivers/sound/audio.c
linux-2.4.0
speaker instead.
Chris
--- linux-vanilla/drivers/sound/sscape.cSun Nov 12 02:33:14 2000
+++ linux-2.4.0/drivers/sound/sscape.c Sat Jan 6 17:58:03 2001
@@ -671,7 +673,7 @@
return;
}
- if (sscape_is_pnp == 0) {
+ if
quested.
> Because there may be multiple copies of the same block in the
> journal, one should take the newest one that can be found in
> the last commited transaction.
>
> IMHO Chris Mason already wrote such code, at least he talked about
> it...
>
Talked about it, but never
On Sunday, January 07, 2001 03:48:41 AM +0100 Daniel Phillips
<[EMAIL PROTECTED]> wrote:
> A null buffer was passed by kupdate_one_transaction (looks like a
> Reiserfs function) to __refile_buffer. Chris?
>
Known bug, there should be another reiserfs release soon that include
d of isapnp_info_device->activate() and
isapnp_info_device->deactivate()? The former don't try to acquire the
mutex, and are precisely what the "activate" and "deactivate" /proc
commands invoke anyway.
Cheers,
Chris
This is the output from /proc/isapnp:
Card 1 &#
On Mon, 8 Jan 2001, Matthias Juchem wrote:
> Hi Chris,
>
> Comparing the Changes document for 2.4.0 against the one from 2.3.11 one
> can see that many requirements were removed. Nine out of 22 are still
> there.
> Have the removed ones been unnecessary or only less
&ad1848_mixer_operations,
Or maybe the sound_install_() functions should accept "owner"
parameters, so that the static structs could become "const"?
Cheers,
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
iles dns
protocols: files
services: files
ethers: files
rpc:files
netgroup: files
What else could effect that?
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "you look like you are wearing a tuxedo." The sec
Hi,
This is a revised version of my ad1848 patch; instead of modifying the
static structures, update the "owner" fields in the audio_devs[] and
mixer_devs[] structures instead.
Chris
--- linux-vanilla/drivers/sound/ad1848.cFri Aug 11 16:26:43 2000
+++ linux-2.4.0-ac3/dri
s_page;
> + }
^
This doesn't look right...
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
libc-2.2, but this problem also existed in 2.1.x (which I had
installed when I went to the 2.3 kernels that exposed this problem).
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "you look like you are wearing a tuxedo.&qu
dirty until
try_to_free_buffers writes it again.
> + submit_bh(WRITE, bh);
> + }
> + bh = bh->b_this_page;
> + } while (bh != head);
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
tion in mpu401.c.
It might be "interesting" to redeclare all the static struct
mixer_operations as "const", along with the argument in
sound_install_mixer(), and see exactly how many sound modules scream
in pain. Maybe too interesting for 2.4.1... :-) ?
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
aging to do better, due to
keeping the more useful pages in RAM better. I have no explanation.
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
into this server.
Another interesting thing I have noticed about this delay. If I remove
the data in the password field from the shadow file ("username::...")
there is no pause during login.
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "
right patch from Jens, it doesnt suck anymore. )
Is this "right patch from Jens" on the radar for 2.4 inclusion?
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Hi,
This patch makes the mpu401_synth_operations structure respect
attach_mpu401()'s "owner" parameter. This should prevent more sound
module from being accidentally unloaded.
Cheers,
Chris
--- linux-vanilla/drivers/sound/mpu401.cFri Jan 5 23:14:08 2001
+++ linux-2.
On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>>> EIP; c013f911<=
> Trace; c013f706
> Trace; c0136e01
The buffer reiserfs is sending to filldir is big enough for
the huge file name, so I think the real fix should be done in VFSland.
But, in
On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann <[EMAIL PROTECTED]> wrote:
>>> EIP; c013f911<=
> Trace; c013f706
> Trace; c0136e01
>
Here is a patch against our 2.4 code (3.6.25) that does the
same as the patch posted for 3.5.29:
-chr
problem is too easy to reproduce and
> VERY dangerous I think alerting people to this problem is in order.
>
Sorry, a quick attempt at reproducing on 2.2.17 and 2.2.19 kernels did not
cause an oops. Could you please send me a decoded version of the oops to
help track things down?
thanks,
C
ge
DMA 1 8-bit byte-count compatible
DMA 0,3 8-bit byte-count compatible
...
And uses these module options:
options sscape irq=5 dma=1 io=0x338 mpu_io=0x330 mpu_irq=9
Cheers,
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
Mike Harrold <[EMAIL PROTECTED]> writes:
[...]
My feeling is that it shouldn't matter if you use <<2 or *4 even if the
compiler optimises - one would hope that the compiler would optimise to
the fastest in both directions.
I agree this should be left to the compiler. The programmer shoul
the buffer sent from userspace, I don't see how
we stay in bounds.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Wednesday, January 10, 2001 07:02:08 PM +0300 "Vladimir V. Saveliev"
<[EMAIL PROTECTED]> wrote:
> Hi
>
> Chris Mason wrote:
>
>> On Wednesday, January 10, 2001 02:32:09 AM +0100 Marc Lehmann
>> <[EMAIL PROTECTED]> wrote:
>>
>> &g
On Wednesday, January 10, 2001 12:38:34 PM -0500 Alexander Viro
<[EMAIL PROTECTED]> wrote:
> On Wed, 10 Jan 2001, Chris Mason wrote:
>
>> In filldir, I don't like the line where we ((char *)dirent += reclen ;
>> If reclen is much larger than the buffer sent from
Hi,
This is an incredibly boring patch that just adds "const" to some of
the ISA-PNP function prototypes. It compiles cleanly with gcc-2.95.2.
Cheers,
Chris
--- linux-vanilla/include/linux/isapnp.hSun Dec 31 19:11:06 2000
+++ linux-2.4.0-ac3/include/linux/isapnp.h Wed Ja
nstead of nobody because its programmer used pthreads and assumed
that setuid() would affect all threads.
I pointed this out to the author and Red Hat, and it was fixed in
pidentd 3.0.11 and Red Hat 6.2.
-Chris Wing
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe
ow includes the
coprocessor too.
Cheers,
Chris
--- linux-vanilla/drivers/sound/audio.c Fri Aug 11 16:26:43 2000
+++ linux-2.4.0-ac3/drivers/sound/audio.c Wed Jan 10 23:53:23 2001
@@ -21,6 +21,9 @@
* Daniel Rodriksson: reworked the use of the device specific copy_user
*
On Wednesday, January 10, 2001 05:56:09 PM -0200 Marcelo Tosatti
<[EMAIL PROTECTED]> wrote:
>
> Hi Chris,
>
> It seems there is a possible deadlock condition with your patch which
> changes flush_dirty_buffers() to use ->writepage (something which we
> _definately_
901 - 1000 of 8373 matches
Mail list logo
