Convert the cciss driver to compat_ioctl. This cleans up a lot
of code.
I don't have such hardware thus this is only compile tested.
This requires the block device compat_ioctl patch I sent earlier.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
diff -u
Hi,
Here is a trivial patch to fix a typo in the arch/x86_64/Kconfig file.
Diffed against linux-2.6.11-rc1. Please apply.
Signed-off-by: Vadim Lobanov [EMAIL PROTECTED]
diff -Nru a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
--- a/arch/x86_64/Kconfig 2005-01-12 00:13:13.0 -0800
+++
On Tue, Jan 18, 2005 at 02:54:24AM +, Daniel Drake wrote:
Retry up to 20 times if mounting the root device fails. This fixes booting
from usb-storage devices, which no longer make their partitions immediately
available.
This should allow booting from root=/dev/sda1 and root=8:1 style
* Jack O'Quin [EMAIL PROTECTED] wrote:
In the absence of any documentation, I'm guessing about storing the
nice value in the priority field of the sched_param struct. But, I
have not been able to figure out how to make that work.
the call you need is:
setpriority(PRIO_PROCESS, tid,
On Mon, Jan 17, 2005 at 04:02:15PM -0800, Randy.Dunlap wrote:
Al Viro wrote:
On Tue, Jan 18, 2005 at 02:54:24AM +, Daniel Drake wrote:
Retry up to 20 times if mounting the root device fails. This fixes
booting
from usb-storage devices, which no longer make their partitions
Randy.Dunlap wrote:
Al Viro wrote:
On Tue, Jan 18, 2005 at 02:54:24AM +, Daniel Drake wrote:
Retry up to 20 times if mounting the root device fails. This fixes
booting
from usb-storage devices, which no longer make their partitions
immediately
available.
Sigh... So we can very well get
On Mon, Jan 17, 2005 at 05:46:35PM -0200, Marcelo Tosatti wrote:
On Sun, Jan 16, 2005 at 12:35:30AM +0100, Mario Holbe wrote:
Could somebody please explain this to me? Is this intentional?
No
Thanks :)
Can you please turn readahead off (hdparm -a 0 /dev/hdg) and repeat the tests?
The
vlobanov [EMAIL PROTECTED] writes:
diff -Nru a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
--- a/arch/x86_64/Kconfig 2005-01-12 00:13:13.0 -0800
+++ b/arch/x86_64/Kconfig 2005-01-17 23:57:22.0 -0800
@@ -59,7 +59,7 @@
This is useful for kernel debugging when your
Hello linux-experts,
From which kernel series onwards O(1) scheduler was
incorporated into linux? I want a 2.4.x kernel with
O(1) scheduler. But I downloaded 2.4.28 scheduler from
kernel.org. It was the latest one in the list in the
2.4.x series. But it misses O(1) scheduler. Where can
I get a
Alan Cox writes:
On Llu, 2005-01-17 at 14:29, Egbert Eich wrote:
OK, sounds promising. The changed Xserver pieces are in HEAD of the
X.Org tree. I'll see that I make the necessary adjustments to have
a soft detection if you can give me a version number of the kernel
which will have
And almost all of them are pure software-patents and probably prior art.
Thus they are - at least in Europe - not relevant and actually illegal
if you believe in the current European patent law as defined by the
European Patent Convention (see 52(2) for details).
Hopefully nothing will change
On Mon, 2005-01-17 at 18:57 -0500, Karim Yaghmour wrote:
Thomas Gleixner wrote:
If we add another hardwired implementation then we do not have said
benefits.
Please stop handwaving. Folks like Andrew, Christoph, Zwane, Roman,
and others actually made specific requests for changes in the
On Tue, Jan 18, 2005 at 02:47:08AM +0100, Andi Kleen wrote:
Juho Snellman [EMAIL PROTECTED] writes:
2.6.10 changed the behaviour of the int3 instruction on x86-64. It
used to result in a SIGTRAP, now it's a SIGSEGV in both native and
32-bit legacy modes. This was apparently caused by the
Helge Hafting [EMAIL PROTECTED] wrote:
The USB block driver should know that 10s (or whatever) hasn't yet
passed, and simply
block any attempt to access block devices (or scan for them) knowing
that it will
not work yet, but any device will be there after the pause. A root mount
on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thats your answer then. HyperThreading makes one cpu act as two (with a
suitable performance increase for some workloads)
This doesn't explain why it stopped booting on his computer...
I guess he doesn't have the right workload for the
omes wrote:
I suddenly couldn't send to the mailinglist any longer.. I'm going back to
2.4.28 for now. My 4GB of RAM support was already turned off.. Good luck
further. Here is my mail:
On Monday 17 January 2005 22:34, you wrote:
omes wrote:
I have the same problem as you. At least our problems
Yes its a bug, we turn trap 3 into interrupt gates to ensure that it is not
preemtable.
Is the patch ok for you?
-Andi
Like this patch.
Index: linux/arch/x86_64/kernel/traps.c
===
---
[cyrlat]
,, ,
, ,
.
, ,
:
-
[, , , ]
-,
,.
-
-
-
:
E-mail: [EMAIL PROTECTED] Tel: +420776074699,
Czech Republic Prague 1 Vaclavske nam. 37 CERNIS s.r.o.
Your mail is linux-kernel@vger.kernel.org
On Tue, 2005-01-18 at 09:37 +0100, Bernhard Schauer wrote:
And almost all of them are pure software-patents and probably prior art.
Thus they are - at least in Europe - not relevant and actually illegal
if you believe in the current European patent law as defined by the
European Patent
On Tue, Jan 18, 2005 at 09:19:27AM +, Christoph Hellwig wrote:
+long compat_blkdev_ioctl(struct file *file, unsigned cmd, unsigned long
arg)
+{
+ struct block_device *bdev = file-f_dentry-d_inode-i_bdev;
+ struct gendisk *disk = bdev-bd_disk;
+ int ret = -ENOIOCTLCMD;
+
On Tue, Jan 18, 2005 at 10:31:58AM +0100, Andi Kleen wrote:
- please don't introduce a new API with the BKL held.
Nope, I'm not going to audit zillions of low level functions for this.
So just stick a lock_kernel() unlock_kernel() into the handler, it's
not like there's more than a handfull
This patch makes some needlessly global code static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
diffstat output:
drivers/input/evbug.c |4 ++--
drivers/input/gameport/emu10k1-gp.c |4 ++--
drivers/input/gameport/fm801-gp.c |4 ++--
This patch makes two needlessly global functions static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
diffstat output:
drivers/block/umem.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
This patch was already sent on:
- 29 Nov 2004
---
This patch makes a needlessly global variable static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
This patch was already sent on:
- 29 Nov 2004
--- linux-2.6.10-rc1-mm3-full/drivers/block/xd.c.old2004-11-06
20:20:25.0 +0100
+++ linux-2.6.10-rc1-mm3-full/drivers/block/xd.c
Hello,
i dont understand the current argument so would prefere not to enter it.
But it triggered my curiosity about current loop-aes security.
3 years ago i published a paper describing how an attacker would be able
to modify the content of the encrypted device without being detected.
On Tue, Jan 18, 2005 at 09:36:45AM +, Christoph Hellwig wrote:
On Tue, Jan 18, 2005 at 10:31:58AM +0100, Andi Kleen wrote:
- please don't introduce a new API with the BKL held.
Nope, I'm not going to audit zillions of low level functions for this.
So just stick a lock_kernel()
I haven't found any way how xfrm_policy_delete could be called from
modular code in 2.6.11-rc1-mm1.
Unless I'm wrong or a patch for a modular usage is pending, I'm
therefore suggesting this patch for removing the EXPORT_SYMBOL.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
Hi, Andi!
Quoting r. Andi Kleen ([EMAIL PROTECTED]) [PATCH] Some fixes for compat ioctl:
While doing some compat_ioctl conversions I noticed a few issues
in compat_sys_ioctl:
- It is not completely compatible to old -ioctl because
the traditional common ioctls are not checked before it.
Attached patch is against 2.6.11-rc1-bk5
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Add a missing security hook for compatibility ioctl.
diff -rup linux-2.6.10-orig/fs/compat.c linux-2.6.10-ioctl-sym/fs/compat.c
--- linux-2.6.10-orig/fs/compat.c 2005-01-18 10:58:33.609880024
Attached patch is against 2.6.11-rc1-bk5
A piece is copied from Andi's patch, too. No idea if
his SOB should be here too. Here it is just in case.
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
Make common ioctls apply for compat_ioctl.
diff -rup
On Tue, Jan 18, 2005 at 12:48:16PM +0200, Michael S. Tsirkin wrote:
Attached patch is against 2.6.11-rc1-bk5.
It is split out from Andi's big patch.
It is really unchanged so I dont put a signed-off-by here.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
SIOCDEVPRIVATE ioctl command only
On Mon, Jan 17, 2005 at 05:46:35PM -0200, Marcelo Tosatti wrote:
On Sun, Jan 16, 2005 at 12:35:30AM +0100, Mario Holbe wrote:
mounting an ext2 (ext3 as well) filesystem seems to modify the
block device's EOF behaviour: before the mount the device returned
EOF, after the mount it doesn't
This is just a split off from Andi's patch, so I didnt add my SOB here.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
Since its too early to deprecate (un)register_ioctl32_conversion,
add a comment for that time when we do.
diff -rup linux-2.6.10-orig/fs/compat.c
Bill Davidsen wrote:
Nick Sanders wrote:
For me when running growisofs with user permissions on 2.6.10 (ide-cd) it
works perfectly 1st time but 2nd time fails with the error below. It works
fine when run as root.
:-( unable to PREVENT MEDIA REMOVAL: Operation not permitted
As an aside audio cd
- if (cmd = SIOCDEVPRIVATE cmd = (SIOCDEVPRIVATE + 15)) {
+ if (S_ISSOCK(filp-f_dentry-d_inode-i_mode)
+ cmd = SIOCDEVPRIVATE cmd = (SIOCDEVPRIVATE + 15)) {
error = siocdevprivate_ioctl(fd, cmd, arg);
Maybe this should move into a new sock_compat_ioctl()
I believe that IBM is simply responding to the recent study that Linux
violates more than 283 patents. Regardless of the truth to that study,
this is IBM's way of stating that the 60 that they hold will not be used
against Linux or other open source projects.
Bernd Petrovitsch wrote:
On Mon,
Signed-off-by: Michael S. Tsirkin [EMAIL PROTECTED]
Make unlocked_ioctl and compat_ioctl behave symmetrically -
check them first thing, and always require returning ENOIOCTLCMD
on error from unlocked_ioctl, same as we do for compat_ioctl.
This also makes it possible to override *all* ioctl
On Mon, 17 Jan 2005, H. Peter Anvin wrote:
Or does kdb not have a client at all? (If so, I have no sympathy for it.)
Peter, it was very easy for you to call my emails rants and not even
funny but the above statement is displaying complete ignorance of what
kdb actually is :) So, instead of
On Tuesday 18 January 2005 11:04, James Bruce wrote:
I believe that IBM is simply responding to the recent study that Linux
violates more than 283 patents. Regardless of the truth to that study,
The study said that it may violate patents; but that those patents may
not be enforceable due to
Hello,
Im a developer of yet another kernel tracer, LKST. I and co-developers
are very glad to hear that LTT was merged into -mm tree and to talk
about the kernel tracer on this ML. Because we think that the kernel
event tracer is useful to debug Linux systems, and to improve the kernel
Christoph Hellwig wrote:
: I have a better patch than the one I gave you (attached below). If you
: send me a mail with steps to reproduce your remaining problems I'll put
: this very high on my TODO list after christmas. Btw, any chance you could
: try XFS CVS (which is at 2.6.9) + the patch
On Tue, Jan 18, 2005 at 08:19:18PM +0900, Masami Hiramatsu wrote:
Hello,
I?m a developer of yet another kernel tracer, LKST. I and co-developers
are very glad to hear that LTT was merged into -mm tree and to talk
about the kernel tracer on this ML. Because we think that the kernel
event
On Tue, Jan 18, 2005 at 11:55:47AM +0100, Andries Brouwer wrote:
I suppose that what happens is the following:
mounting sets the blocksize to 4096.
After reading 9992360 sectors, reading the next block means reading
the next 8 sectors and that fails because only 6 sectors are left.
Test that
On Tue, 2005-01-18 at 11:25 +, Tigran Aivazian wrote:
However, this highlighted a more serious problem in the x86_64 kernel (or
more likely in the kdb patch) --- the kernel compiled with -g panics when
you try to return from kdb after hitting a breakpoint. This is a bug and
I'll
Hi Andries,
On Tue, Jan 18, 2005 at 11:55:47AM +0100, Andries Brouwer wrote:
On Mon, Jan 17, 2005 at 05:46:35PM -0200, Marcelo Tosatti wrote:
On Sun, Jan 16, 2005 at 12:35:30AM +0100, Mario Holbe wrote:
mounting an ext2 (ext3 as well) filesystem seems to modify the
block device's EOF
On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote:
So this is either not a Linux error and not a disk error, its just that the
use with filesystem then direct access is a unfortunate combination.
What would be the correct fix for this for this, if any?
Well, I personally think
On Mon, Jan 17, 2005 at 10:27:22PM -0800, Greg KH wrote:
On Tue, Jan 18, 2005 at 02:20:31AM +, Matthew Wilcox wrote:
Greg, you're merging a lot of patches that aren't going through
the linux-pci mailing list for review. Please redirect patches that
are sent to you directly so others
Hi,
ChangeLog
* provide huge page fault handler and related things
snip
Index: linux-2.6.9/fs/hugetlbfs/inode.c
===
--- linux-2.6.9.orig/fs/hugetlbfs/inode.c 2004-10-18 14:55:07.0
-0700
+++
Forward compat_ioctl through the frame buffer layer.
This is needed for a followup patch.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
diff -u linux-2.6.11-rc1-bk4/drivers/video/fbmem.c-o
linux-2.6.11-rc1-bk4/drivers/video/fbmem.c
--- linux-2.6.11-rc1-bk4/drivers/video/fbmem.c-o
got an Oops the same time for 9 days, at the same EIP:
ksymoops 2.4.9 on i686 2.4.28-x97. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.28-x97/ (default)
-m /boot/System.map-2.4.28-x97 (default)
kernel: 1Unable to
Convert the sis framebuffer driver to compat ioctl.
Requires generic framebuffer compat_ioctl patch I posted
earlier on l-k.
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
diff -u linux-2.6.11-rc1-bk4/drivers/video/sis/sis.h-o
linux-2.6.11-rc1-bk4/drivers/video/sis/sis.h
---
On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote:
I suppose that what happens is the following:
mounting sets the blocksize to 4096.
After reading 9992360 sectors, reading the next block means reading
the next 8 sectors and that fails because only 6 sectors are left.
So
On Tue, Jan 18, 2005 at 12:47:01PM +0100, Mario Holbe wrote:
If you want to restore the device to full size, use
blockdev --setbsz 512.
Does that in any way hurt, if a filesystem is just mounted?
It is a bad idea to change the blocksize of a mounted filesystem.
-
To unsubscribe from this
This patch for 2.6.11-rc1 provides a method of providing real time
scheduling to unprivileged users which increasingly is desired for
multimedia workloads.
It does this by adding a new scheduling class called SCHED_ISO or
Isochronous scheduling which means same time scheduling. This class
does not
On Tue, 18 Jan 2005, Tigran Aivazian wrote:
I already solved this paricular problem. And the solution is (but don't tell
me you knew it, for then why didn't you tell anyone) simply --- compile the
kernel with -g and that includes enough debug information to be able to
decode the stack content
On Tue, 18 Jan 2005 18:52:55 +1100,
Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
On Tue, 2004-12-28 at 22:17 +0100, Sam Ravnborg wrote:
2 Add in_gate_area_no_task() for use from places where no task is valid.
Can you back that out ? Or at least explain why you need to add this
no_task
Andrew Morton wrote:
Helge Hafting [EMAIL PROTECTED] wrote:
The USB block driver should know that 10s (or whatever) hasn't yet
passed, and simply
block any attempt to access block devices (or scan for them) knowing
that it will
not work yet, but any device will be there after the pause. A
Hi,
If my system needs the OOM killer, it's usurally unresponsive to most
userspace applications. A normal daemon would be swapped out before the
runaway dhcpd grows larger than the web cache. It would have to be a mlocked
RT task started from early userspace. It would be difficult to set up
Sorry, it was a red herring, namely my module's Makefile still had
-mregparm=0 in CFLAGS, so that is why kdb showed it's arguments
correctly (and then paniced on the way out).
So we still have to deal with DWARF2 data then... Ok, will look into it.
Kind regards
Tigran
On Tue, 18 Jan 2005,
Hello, list.
NOTE: I am not subscribed, so please CC me in any of your replies.
I recently set up a machine featuring an Intel ICH6 desktop board
with two 200GB Seagates (ST3200822AS) in mirrored volume, AHCI mode,
with linux kernel 2.6.10 and ext3.
After a relatively small amount of I/O (for
On Tue, Jan 18, 2005 at 01:37:08PM +0100, Andries Brouwer wrote:
On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote:
I suppose that what happens is the following:
mounting sets the blocksize to 4096.
After reading 9992360 sectors, reading the next block means reading
On Sat, 2005-01-15 at 15:07, Serge E. Hallyn wrote:
The audit control messages are sent over netlink. Permission checks
are done on the process receiving the message, which may not be the
same as the process sending the message. This patch switches the
netlink_send security hooks to
Normally, this problem associated with drives over 32GB or 127GB on a
controller that cannot support it. It was not discussed here, I was
wondering if that is the problem, if it is not, what type of Hard Drive
is giving you these problems?
Thanks.
-Original Message-
From: [EMAIL
On Tue, Jan 18, 2005 at 08:42:08AM -0500, Piszcz, Justin Michael wrote:
Normally, this problem associated with drives over 32GB or 127GB on a
controller that cannot support it. It was not discussed here, I was
wondering if that is the problem, if it is not, what type of Hard Drive
is giving
Okay but what hard drive model and IDE Chipset/Controller are you using?
Thanks!
-Original Message-
From: Mario Holbe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 18, 2005 9:02 AM
To: Piszcz, Justin Michael
Cc: Marcelo Tosatti; Andries Brouwer; linux-kernel@vger.kernel.org
Subject:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andi Kleen wrote:
| Convert the sis framebuffer driver to compat ioctl.
|
| Requires generic framebuffer compat_ioctl patch I posted
| earlier on l-k.
|
| Signed-off-by: Andi Kleen [EMAIL PROTECTED]
Signed-off-by: Thomas Winischhofer [EMAIL PROTECTED]
On Tue, Jan 18, 2005 at 09:05:05AM -0500, Piszcz, Justin Michael wrote:
Okay but what hard drive model and IDE Chipset/Controller are you using?
VIA vt82c686b onboard
PDC20269 (Promise U133TX2) on PCI
hda: WDC WD400EB-00CPF0, ATA DISK drive
hdc: IC35L080AVVA07-0, ATA DISK drive
hdd: HL-DT-ST
dmesg produces the following :
oom-killer: gfp_mask=0xd0
DMA per-cpu:
cpu 0 hot: low 2, high 6, batch 1
cpu 0 cold: low 0, high 2, batch 1
Normal per-cpu:
cpu 0 hot: low 32, high 96, batch 16
cpu 0 cold: low 0, high 32, batch 16
HighMem per-cpu:
cpu 0 hot: low 30, high 90, batch 15
cpu 0 cold:
Why not just use dd if=/dev/xxx `blockdev --getbsz /dev/xxx` ...?
Sytse
-
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
These are patches designed to improve system responsiveness. It is
configurable to any workload but the default ck* patch is aimed at the
desktop and ck*-server is available with more emphasis on serverspace.
http://ck.kolivas.org/patches/2.6/2.6.10/2.6.10-ck5/
web:
http://kernel.kolivas.org
Is the problem with the drive on the promise board or the drive on the
VIA chipset?
(from google)
Soyo SY-7VBA133U VIA 694T SY-7VBA133U : ComputerHQ.com3
... Main Specifications. Product Description, SOYO Socket 370
SY-7VBA133U - mainboard -
ATX - Pro133T. ... Audio Output, Sound card - VIA
Looks like you ran out memory and the OOM-killer began killing
processes.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick
Sent: Tuesday, January 18, 2005 9:17 AM
To: linux-kernel@vger.kernel.org
Subject: What Would Cause This :
dmesg produces the
Hi,
Andi Kleen wrote:
On Tue, Jan 18, 2005 at 08:19:18PM +0900, Masami Hiramatsu wrote:
Hello,
I?m a developer of yet another kernel tracer, LKST. I and co-developers
are very glad to hear that LTT was merged into -mm tree and to talk
about the kernel tracer on this ML. Because we think that the
Con Kolivas wrote:
This patch for 2.6.11-rc1 provides a method of providing real time
scheduling to unprivileged users which increasingly is desired for
multimedia workloads.
I should have mentioned. Many thanks to Alex Nyberg for generous
debugging help.
Cheers,
Con
signature.asc
Description:
Hi all,
the input subsystem is using call_usermodehelper directly, which breaks
all sorts of assertions especially when using udev.
And it's definitely going to fail once someone is trying to use netlink
messages for hotplug event delivery.
To remedy this I've implemented a new sysfs class
This patch implements the core changes in drivers/input/input.c.
A new sysfs class 'input_device' is added as a representation of
struct input_dev.
Cheers,
Hannes
--
Dr. Hannes Reinecke [EMAIL PROTECTED]
SuSE Linux AG S390 zSeries
Maxfeldstraße 5
Implement proper class names for input drivers.
Cheers,
Hannes
--
Dr. Hannes Reinecke [EMAIL PROTECTED]
SuSE Linux AG S390 zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
On Tue, Jan 18, 2005 at 09:24:03AM -0500, Piszcz, Justin Michael wrote:
Is the problem with the drive on the promise board or the drive on the
VIA chipset?
Oh, please - no FUD. There is no problem, and we understand in detail
what happens and why it happens. There is no need for any
Not trying to spread FUD, I am just explaining I had the same issue and
that was the resolution.
-Original Message-
From: Andries Brouwer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 18, 2005 10:04 AM
To: Piszcz, Justin Michael
Cc: Mario Holbe; linux-kernel@vger.kernel.org
Subject:
On Tue, Jan 18, 2005 at 12:30:32PM +1100, Rusty Russell wrote:
On Tue, 2005-01-18 at 00:06 +0530, Ravikiran G Thirumalai wrote:
...
The allocator can be easily modified to use __per_cpu_offset[] table at a
later
stage by:
1. Allocating ALIGN(__per_cpu_end - __per_cpu_start, PAGE_SIZE)
Andi Kleen wrote:
As Brian said the device he was working with would just not answer,
leading to a bus abort. This would get on a PC.
You could simulate this if you want, although I think a EBUSY or EIO
is better.
Alan - are you satisfied with the most recent patch, or would you prefer
On Tue, Jan 18, 2005 at 03:17:07PM +0100, Sytse Wielinga wrote:
Why not just use dd if=/dev/xxx `blockdev --getbsz /dev/xxx` ...?
because it doesn't work, as I've demonstrated in
Message-ID: [EMAIL PROTECTED]
[EMAIL PROTECTED]:~# dd if=/dev/hdg7 of=/dev/null bs=512
attempt to access beyond
On Tue, Jan 18, 2005 at 09:24:03AM -0500, Piszcz, Justin Michael wrote:
Is the problem with the drive on the promise board or the drive on the
VIA chipset?
The problem is with each drive on each controller. The problem is even
with no drive on no controller - as I've shown to you with my loop
Greetings list.
I'm curious about something which looks like an error in the mpc8xx
build of the latest 2.6.11-rc1 kernel.
Firstly, I have a 2.4.28-rc1 which builds just fine for this arch,
however from an almost totally similar kernel config as was used in the
2.4, and with the same compiler,
Hi,
On Mon, 17 Jan 2005, Karim Yaghmour wrote:
With that said, I hope we've agreed that we'll have a callback for
letting relayfs clients know that they need to write the begining of
the buffer event. There won't be any associated reserve. Conversly,
I hope it is not too much to ask to have
Linus,
I would like to try to get these patches into 2.6.11. They add
infrastructure for all ppc sub-archs to use platform_devices instead of
OCP. Additionally, I've converted the 85xx sub-arch and gianfar enet
driver (used by 85xx) over to using platform_device and the new
infrastructure.
System platform_device description, discovery and management:
On most embedded PPC systems we either have a core CPU and chipset
(MPC10x, TSI10x, Marvell, etc.) or a system-on-chip device (4xx, 8xx,
82xx, 85xx, etc.). Some of these sub-archs have been using the On Chip
Peripheral (OCP) driver
Convert MPC8540 ADS, MPC8560 ADS, MPC8555 CDS and SBC8560 reference boards
from using OCP to platform_device.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
diff -Nru a/arch/ppc/platforms/85xx/mpc8540_ads.c
b/arch/ppc/platforms/85xx/mpc8540_ads.c
--- a/arch/ppc/platforms/85xx/mpc8540_ads.c
Infrastructure changes to MPC85xx sub-arch from OCP to platform_device:
* Described all devices available on current MPC85xx CPUs (mem irq)
* Added cpu descriptions for the MPC8540, MPC8541, MPC8541, MPC8555,
MPC8555E, and MPC8560.
* Removed OCP usage from MPC85xx sub-arch
Signed-off-by:
Convert gianfar ethernet driver from using an OCP to platform_device.
Signed-off-by: Kumar Gala [EMAIL PROTECTED]
---
diff -Nru a/drivers/net/gianfar.c b/drivers/net/gianfar.c
--- a/drivers/net/gianfar.c 2005-01-17 22:31:44 -06:00
+++ b/drivers/net/gianfar.c 2005-01-17 22:31:44 -06:00
@@
On Tue, Jan 18, 2005 at 10:07:27AM -0500, Piszcz, Justin Michael wrote:
Not trying to spread FUD, I am just explaining I had the same issue and
that was the resolution.
Well, *if* the reason of your issue was the same as the reason of
my issue (what could be, but must not be), you were in the
Fruhwirth Clemens wrote:
Nothing about kernel crypto is backdoored. If Ruusu thinks different, he
should show me source code. Till then, treat it as FUD.
I have been submitting fix for this weakness to mainline mount (part of
util-linux package) since 2001, about 2 or 3 times a year. Refusing
jerome etienne wrote:
3 years ago i published a paper describing how an attacker would be able
to modify the content of the encrypted device without being detected.
http://off.net/~jme/loopdev_vul.html
i was just curious about the current state of loop-aes. Is it still
vulnerable to this
Cal wrote:
Con Kolivas wrote:
Comments and testing welcome.
There's a collection of test summaries from jack_test3.2 runs at
http://www.graggrag.com/ck-tests/ck-tests-0501182249.txt
Tests were run with iso_cpu at 70, 90, 99, 100, each test was run twice.
The discrepancies between consecutive
Con Kolivas wrote:
Comments and testing welcome.
There's a collection of test summaries from jack_test3.2 runs at
http://www.graggrag.com/ck-tests/ck-tests-0501182249.txt
Tests were run with iso_cpu at 70, 90, 99, 100, each test was run twice.
The discrepancies between consecutive runs (with same
Hi,
On Tue, 18 Jan 2005 15:59:35 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Implement proper class names for input drivers.
This patch probably should probably use atomic_inc in case we ever
have non-serialized probe functions.
But the real question is whether we really need class
On Tue, Jan 18, 2005 at 04:20:06PM +0100, Mario Holbe wrote:
On Tue, Jan 18, 2005 at 03:17:07PM +0100, Sytse Wielinga wrote:
Why not just use dd if=/dev/xxx `blockdev --getbsz /dev/xxx` ...?
because it doesn't work, as I've demonstrated in
Message-ID: [EMAIL PROTECTED]
[EMAIL
Hello,
I have ported the prog/hotplug/m7101.c module from lm_sensors for kernel 2.6.
Here is the patch.
EnricoB
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
On Tue, Jan 18, 2005 at 04:55:34PM +0100, I wrote:
multiples of the block size. The 2.6 kernel does not have this problem; it
appears to accept partial blocks, and doesn't even appear to calculate the
device size (blockdev --getsz and --getsize return 0 on my machine.)
Cal [EMAIL PROTECTED] writes:
There's a collection of test summaries from jack_test3.2 runs at
http://www.graggrag.com/ck-tests/ck-tests-0501182249.txt
Tests were run with iso_cpu at 70, 90, 99, 100, each test was run
twice. The discrepancies between consecutive runs (with same
parameters)
1 - 100 of 544 matches
Mail list logo
