[PATCH 1/5] compat_ioctl call seems to miss a security hook

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

[PATCH 3/5] make common ioctls apply for compat.

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

Re: [PATCH 2/5] socket ioctl fix (from Andi)

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

[PATCH 4/5] reminder comment about register_ioctl32_conversion

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

Re: Unable to burn DVDs

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

Re: [PATCH 2/5] socket ioctl fix (from Andi)

> > - 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

Re: IBM Patents

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

[PATCH 5/5] symmetry between compat_ioctl and unlocked_ioctl

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

Re: [discuss] booting a kernel compiled with -mregparm=0

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

Re: IBM Patents

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

Re: 2.6.11-rc1-mm1

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 tracer is useful to debug Linux systems, and to improve the kernel

Re: XFS: inode with st_mode == 0

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

Re: 2.6.11-rc1-mm1

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 >

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: [discuss] booting a kernel compiled with -mregparm=0

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: PCI patches not being reviewed

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

Re: Hugepages demand paging V2 [1/8]: hugetlb fault handler

Hi, > ChangeLog > * provide huge page fault handler and related things > 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 > +++

[PATCH] Add compat_ioctl to frame buffer layer

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

2.4.28 Oops in fs/locks.c:time_out_leases()

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: <1>Unable to

[PATCH] Convert sis fb driver to compat_ioctl

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 ---

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

[PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

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

Re: [discuss] booting a kernel compiled with -mregparm=0

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

Re: [patch 0/3] kallsyms: Add gate page and all symbols support

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

Re: [PATCH] Wait and retry mounting root device (revised)

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

Re: User space out of memory approach

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

Re: [discuss] booting a kernel compiled with -mregparm=0

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,

Lock-ups in AHCI (?)

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: [PATCH] Fix audit control message checks

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

RE: 2.4: "access beyond end of device" after ext2 mount

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

RE: 2.4: "access beyond end of device" after ext2 mount

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:

Re: [PATCH] Convert sis fb driver to compat_ioctl

-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

Re: 2.4: "access beyond end of device" after ext2 mount

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

What Would Cause This :

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:

Re: 2.4: "access beyond end of device" after ext2 mount

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

2.6.10-ck5

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

RE: 2.4: "access beyond end of device" after ext2 mount

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

RE: What Would Cause This :

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

Re: [Lkst-develop] Re: 2.6.11-rc1-mm1

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

Re: [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

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:

[PATCH 0/2] Remove input_call_hotplug

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

[PATCH 1/2] Remove input_call_hotplug

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

[PATCH 2/2] Remove input_call_hotplug

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

RE: 2.4: "access beyond end of device" after ext2 mount

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:

Re: [patch 2/2] mm: Reimplementation of alloc_percpu

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,

Re: [PATCH 1/1] pci: Block config access during BIST (resend)

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

ppc32 2.6.x builds for ppc m8xx arch.

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,

Re: 2.6.11-rc1-mm1

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

[PATCH 0/4] ppc32: platform_device conversion from OCP

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.

[PATCH 1/4] ppc32: platform_device conversion from OCP

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

[PATCH 3/4] ppc32: platform_device conversion from OCP

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

[PATCH 2/4] ppc32: platform_device conversion from OCP

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:

[PATCH 4/4] ppc32: platform_device conversion from OCP

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

Re: Announce loop-AES-v3.0b file/swap crypto package

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

Re: Announce loop-AES-v3.0b file/swap crypto package

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

Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

Cal wrote: Con Kolivas wrote: Comments and testing welcome. There's a collection of test summaries from jack_test3.2 runs at Tests were run with iso_cpu at 70, 90, 99, 100, each test was run twice. The discrepancies between consecutive

Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

Con Kolivas wrote: Comments and testing welcome. There's a collection of test summaries from jack_test3.2 runs at Tests were run with iso_cpu at 70, 90, 99, 100, each test was run twice. The discrepancies between consecutive runs (with

Re: [PATCH 2/2] Remove input_call_hotplug

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

Re: 2.4: "access beyond end of device" after ext2 mount

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

PATCH for 2.6: Enabling disabled M7101 device (quirks.c)

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

Re: 2.4: "access beyond end of device" after ext2 mount

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.)

Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

Cal <[EMAIL PROTECTED]> writes: > There's a collection of test summaries from jack_test3.2 runs at > > > Tests were run with iso_cpu at 70, 90, 99, 100, each test was run > twice. The discrepancies between consecutive runs (with same >

Re: [ck] [PATCH][RFC] sched: Isochronous class for unprivileged soft rt scheduling

Con Kolivas <[EMAIL PROTECTED]> writes: > Cal wrote: > > SCHED_ISO > /proc/sys/kernel/iso_cpu . . .: 70 > /proc/sys/kernel/iso_period . : 5 > XRUN Count . . . . . . . . . : 110 > > vs > > SCHED_FIFO > XRUN Count . . . . . . . . . : 114 > XRUN Count . . . . . . . . . : 187 > > vs > >

Re: [RFC] Instrumentation (was Re: 2.6.11-rc1-mm1)

Thomas, Thomas Gleixner wrote: > Yes, I did already start cleaning > > cat ../broken-out/ltt* | patch -p1 -R :D If it gives you a warm and fuzzy feeling to have the last cheap-shot, then I'm all for it, it is of no consequence anyway. And _please_ don't forget to answer this very email with

Re: PCI patches not being reviewed

On Tue, Jan 18, 2005 at 12:21:26PM +, Matthew Wilcox wrote: > 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

[PATCH 0/3] Conversion to compat_ioctl for ALSA drivers

Hi, the following three patches convert the 32bit ioctl layer of ALSA to the new compat_ioctl (and unlocked_ioctl for native ioctls). The first patch covers the basic entries and control API. The second patch is for PCM API. The last one is for other APIs including OSS-emulation modules. After

Re: 2.6.11-rc1-mm1

Tom Zanussi wrote: > I have to disagree. Awhile back, if you remember, I posted a patch to > the LTT daemon that would monitor the trace stream in real time, and > process it using an embedded Perl interpreter, no less: > > http://marc.theaimsgroup.com/?l=linux-kernel=109405724500237=2 > > It

Re: Hugepages demand paging V2 [1/8]: hugetlb fault handler

On Tue, 18 Jan 2005, Hirokazu Takahashi wrote: > > 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 > > +++ linux-2.6.9/fs/hugetlbfs/inode.c

[PATCH 1/3] Conversion to compat_ioctl for ALSA drivers

This patch modifies Kconfig and Makefile to remove snd-ioctl32. It convers to unlocked_ioctl, and adds the compat_ioctl entries. New register/unregister functions for compat ioctl are added. Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]> --- linux/sound/core/Kconfig23 Nov 2004 14:49:03

[PATCH 2/3] Conversion to compat_ioctl for ALSA drivers

This patch converts to unlocked_ioctl and adds the compat ioctl layer for ALSA PCM API. Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]> --- linux/sound/core/pcm.c 30 Nov 2004 19:58:22 - 1.47 +++ linux/sound/core/pcm.c 12 Jan 2005 22:49:21 - @@ -1004,6 +1004,7 @@

Re: PCI patches not being reviewed

On Tue, Jan 18, 2005 at 08:29:08AM -0800, Greg KH wrote: > On Tue, Jan 18, 2005 at 12:21:26PM +, Matthew Wilcox wrote: > > Yes, the PCI Express bridge driver is quite buggy. > > It was posted a number of times to lkml in December, and it was > commented on by a few different people, and the

[PATCH 3/3] Conversion to compat_ioctl for ALSA drivers

The last patch covers the rest of ALSA APIs: hwdep, rawmidi, timer and seq. Also it covers the OSS emulation modules. Signed-off-by: Takashi Iwai <[EMAIL PROTECTED]> --- linux/sound/core/hwdep.c30 Nov 2004 19:58:21 - 1.24 +++ linux/sound/core/hwdep.c18 Jan 2005 14:52:43 -

Re: [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers at a time

On Sat, 15 Jan 2005, Fruhwirth Clemens wrote: > However, developing two different APIs isn't particular efficient. I > know, at the moment there isn't much choice, as J.Morris hasn't commited > to acrypto in anyway. There is also the OCF port (OpenBSD crypto framework) to consider, if

RE: VIA Rhine ethernet driver bug

Hello, > -Original Message- > From: Luc Saillard [mailto:[EMAIL PROTECTED] > Sent: maandag 17 januari 2005 16:46 > To: Marcelo Tosatti > Cc: Udo van den Heuvel; linux-kernel@vger.kernel.org > Subject: Re: VIA Rhine ethernet driver bug > > > On Mon, Jan 17, 2005 at 10:04:27AM -0200,

Re: [PATCH] [request for inclusion] Realtime LSM

Ingo Molnar <[EMAIL PROTECTED]> writes: > * 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

Re: Announce loop-AES-v3.0b file/swap crypto package

On Tue, Jan 18, 2005 at 05:35:48PM +0200, Jari Ruusu wrote: > 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

iswraid and 2.4.x?

--- Marcelo Tosatti <[EMAIL PROTECTED]> wrote: > It seems the general consensus is to merge iswraid, so I'm fine with > it. > > Martins, we are approaching -rc stage, I would prefer the merge to > happen > at the beginning of 2.4.29-pre. Is that fine for you? Marcelo, I seemed to have missed

[QUESTION - FYI] Vectorized CRC calculation

Hi! First, sorry about the so-so topic for the kernel developers...but still there are such things inside :) Currently I am investigating how "they" divide those polynomials and which possibilities exists to use SIMD for such calculations. I have found several papers about how to do it with

pipe performance regression on ia64

David Mosberger pointed out to me that 2.6.11-rc1 kernel scores very badly on ia64 in lmbench pipe throughput test (bw_pipe) compared with earlier kernels. Nanhai Zou looked into this, and found that the performance loss began with Linus' patch to speed up pipe performance by allocating a

Re: Patch to control VGA bus routing and active VGA device.

On Monday, January 17, 2005 7:43 pm, Jon Smirl wrote: > Attached is a patch to control VGA bus routing and the active VGA > device. It works by adding sysfs attributes to bridge and VGA devices. > The bridge attribute is read only and indicates if the bridge is > routing VGA. The attribute on the

Re: security contact draft2 (was Re: security contact draft)

Chris Wright <[EMAIL PROTECTED]> said: [...] > DRAFT [...] > It is preferred that mail sent to the security team is encrypted > with $PUBKEY. Note that $PUBKEY might change, give pointers to the canonical places where you can get the latest version (latest kernel source?). Perhaps indicate

Re: [rfc] i810_audio: offset LVI from CIV to avoid stalled start

On Tue, Jan 18, 2005 at 10:23:23AM +1100, Herbert Xu wrote: > On Mon, Jan 17, 2005 at 04:44:22PM -0500, John W. Linville wrote: > > > > Enemy Territory is available for free (as in beer) download from > Sure, I don't mind trying it out :) > > In the mean time, does this patch fix your problem

PROBLEM: oom-killer bringing machine down in 2.6.10

I posted this to the NFS list and was told to post here. I have a box with 4GB. It's running Red Hat Fedora Core 3 with 2.6.10 as distributed by them. No custom kernel compiling, and no desire :) The problem reported below DID NOT happen with 2.4.21. It did happen also with 2.6.9, and I cannot

Re: iswraid and 2.4.x?

Martins Krikis wrote: --- Marcelo Tosatti <[EMAIL PROTECTED]> wrote: It seems the general consensus is to merge iswraid, so I'm fine with it. Martins, we are approaching -rc stage, I would prefer the merge to happen at the beginning of 2.4.29-pre. Is that fine for you? Marcelo, I seemed to have

Re: pipe performance regression on ia64

On Tue, 18 Jan 2005, Luck, Tony wrote: > David Mosberger: > > > >So, when we run bw_pipe on a low load SMP machine, the kernel running in > >a way load balancer always trying to spread out 2 processes while the > >wake_up_interruptible_sync() is always trying to draw them back into > >1 cpu. > >

Re: iswraid and 2.4.x?

On Tue, Jan 18, 2005 at 09:28:16AM -0800, Martins Krikis wrote: > --- Marcelo Tosatti <[EMAIL PROTECTED]> wrote: > > > It seems the general consensus is to merge iswraid, so I'm fine with > > it. > > > > Martins, we are approaching -rc stage, I would prefer the merge to > > happen > > at the

RE: [PATCH] AC'97 Audio support for Intel ICH7 - 2.6.11-rc1

I have never had an opportunity to test AC'97 modems on ICH6 or ICH7. Sorry, Jason >-Original Message- >From: Takashi Iwai [mailto:[EMAIL PROTECTED] >Sent: Tuesday, January 18, 2005 1:12 AM >To: Gaston, Jason D >Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org >Subject: Re: [PATCH]

Re:[PATCH] PCI: add PCI Express Port Bus Driver subsystem

On Mon, 17 Jan 2005 15:49:08 -0800 Greg KH wrote: > > +int pcie_port_device_register(struct pci_dev *dev) > > +{ > > + struct pcie_device *parent; > > + int status, type, capabilities, irq_mode, i; > > + int vectors[PCIE_PORT_DEVICE_MAXSERVICES]; > > + u16 reg16; > > + > > + /* Get port

Re: iswraid and 2.4.x?

On Tue, Jan 18, 2005 at 01:13:23PM -0500, Jeff Garzik wrote: > Martins Krikis wrote: > >--- Marcelo Tosatti <[EMAIL PROTECTED]> wrote: > > > > > >>It seems the general consensus is to merge iswraid, so I'm fine with > >>it. > >> > >>Martins, we are approaching -rc stage, I would prefer the merge

Re: [2.6 patch] i386/power/cpu.c: remove three unused variables

Followup to: <[EMAIL PROTECTED]> By author:Pavel Machek <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > Hi! > > > The patch below removes three unused variables. > > > > Please check whether this patch is correct, or whether the variables > > should have been used. > > The patch is

<    1   2   3   4   5   6   >