* Re: [patch 2.6.16-mm2 10/9] sched throttle tree extract - kill interactive task feedback loop
From: Mike Galbraith @ 2006-04-05 17:38 UTC (permalink / raw)
To: Ingo Molnar, Andrew Morton; +Cc: lkml, Peter Williams, Nick Piggin, Con Kolivas
In-Reply-To: <1143883915.7617.77.camel@homer>
Greetings,
The patch below stops interactive tasks from feeding off each other
during round-robin.
With this 10th patch in place, a busy server with _default_ throttle
settings (ie tunables may now be mostly unneeded) looks like this:
[root]:# w
18:38:00 up 23 min, 2 users, load average: 10.07, 9.94, 7.50
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
root tty1 18:15 22:12 30.89s 30.84s top d1
root pts/0 18:20 0.00s 0.07s 0.00s w
[root]:# time netstat|grep :81|wc -l
1758
real 0m0.304s
user 0m0.144s
sys 0m0.135s
[root]:# time netstat|grep :81|wc -l
1776
real 0m0.306s
user 0m0.118s
sys 0m0.163s
[root]:# time netstat|grep :81|wc -l
1799
real 0m0.493s
user 0m0.146s
sys 0m0.141s
[root]:#
My desktop still feels just peachy.
Signed-off-by: Mike Galbraith <efault@gmx.de>
--- linux-2.6.16-mm2/kernel/sched.c-9.export_tunables 2006-03-31 13:37:09.000000000 +0200
+++ linux-2.6.16-mm2/kernel/sched.c 2006-04-05 19:22:01.000000000 +0200
@@ -3480,7 +3480,7 @@ go_idle:
queue = array->queue + idx;
next = list_entry(queue->next, task_t, run_list);
- if (!rt_task(next) && interactive_sleep(next->sleep_type)) {
+ if (!TASK_INTERACTIVE(next) && interactive_sleep(next->sleep_type)) {
unsigned long long delta = now - next->timestamp;
if (unlikely((long long)(now - next->timestamp) < 0))
delta = 0;
^ permalink raw reply
* Re: [Qemu-devel] SPARC iommu mapping
From: Blue Swirl @ 2006-04-05 17:36 UTC (permalink / raw)
To: jplatte, qemu-devel
In-Reply-To: <200604051723.17846.lists@naasa.net>
> > To find this problem, I enabled debugging in the esp.c file and printed
>the
> > mapped address (after iommu mapping). In some cases the mapped address
>is
> > zero:
>
> > ESP: DMA address 0beb8000
> > ESP: DMA address 00000000
>
>I didn't find a manual of the SBUS IOMMU. But if I understand the contents
>of
>newer implementations of an IOMMU, each entry in this MMU table has a valid
>bit. And therefore, a 0 entry is invalid. But the current implementation of
>qemu's IOMMU does not check for a valid bit. Where can I find more
>information on this topic? And is a besser IOMMU currently in development?
I don't have any better documentation either, I just coded against what
Proll and Linux expect. But the theory of operation is simple. Much like how
the MMU translates CPU's virtual addresses to physical addresses for memory,
IOMMU translates device virtual memory accesses to physical addresses. The
VA to PA entries are found in a simple page table.
In the case of not finding a valid translation entry, IOMMU can't fault the
device like normal MMU can easily fault the CPU. I don't know what should
happen then, probably put the address to AFAR register and raise some
interrupt, while the device (for example Ethernet controller) waiting for
the data suffers in limbo. I think it would be strange for an OS to rely on
this, so I guess it's a bug somewhere else. My guess for the valid bit is
that it's used in a real IOMMU to select the entries that will be loaded to
its internal translation buffer.
The DMA controllers for both ESP and Lance are within the same page. This
means that in Qemu, DMA controller register accesses for either of them go
to just one of these. It just happens to work, but maybe this causes the
problem. You could try to confirm this by enabling also DEBUG_LANCE and see
if there is troublesome activity in the Lance direction near the bad
accesses.
Can you provide a test case so that I could try it as well?
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
^ permalink raw reply
* Re: FAQ entry for loopback mounting
From: Ralph Siemsen @ 2006-04-05 17:36 UTC (permalink / raw)
To: David Woodhouse; +Cc: linux-mtd
In-Reply-To: <1144258058.6227.90.camel@pmac.infradead.org>
David Woodhouse wrote:
> We _are_ being lenient. If you say 'k' or 'M' instead of 'Ki' or 'Mi'
> then you are going to get the powers of ten which you asked for... which
> is almost certainly _not_ what you wanted. Giving you powers of two is
> not an option. So it's best not to accept it at all.
No, if you give it "k" only, then it multiples by 1024, but because
there is no "i", it does not advance *endp, and then parse_num() returns
-EINVAL because it sees trailing garbage. So just "k" is not accepted
at all, which is not "leniant" in my books.
-R
^ permalink raw reply
* Re: net devices no longer renamed [Re: Linux 2.6.17-rc1]
From: Tomasz Torcz @ 2006-04-05 17:36 UTC (permalink / raw)
To: linux-hotplug
In-Reply-To: <20060405073405.GA7036@irc.pl>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Wed, Apr 05, 2006 at 01:48:47PM +0600, Alexander E. Patrakov wrote:
> Tomasz Torcz wrote:
> >% cat /etc/udev/rules.d/sieciowki.rules
> ># sieciowki
> >KERNEL="eth*", SYSFS{address}="00:07:e9:15:0e:cb", NAME="ep0",
> >RUN+="/etc/dev.d/net/ep0-up.dev"
> >KERNEL="eth*", SYSFS{address}="00:50:8d:e9:ec:c1", NAME="nf",
> >RUN+="/etc/dev.d/net/nf-up.dev"
>
> Does adding the following rule at the very top help? (Yes I know that it is
> supposed to be fixed in linux-2.6.16)
>
> ACTION=="add", SUBSYSTEM=="net", WAIT_FOR_SYSFS="address"
No.
--
Tomasz Torcz RIP is irrevelant. Spoofing is futile.
zdzichu@irc.-nie.spam-.pl Your routes will be aggreggated. -- Alex Yuriev
[-- Attachment #2: Type: application/pgp-signature, Size: 231 bytes --]
^ permalink raw reply
* Re: Throttling NAT interface
From: Casey Scott @ 2006-04-05 17:35 UTC (permalink / raw)
To: Randy Grimshaw; +Cc: netfilter
Thanks for the response. Will using iptables in that
manner cause the firewall to just drop the packets that
arrived after the limit has been reached? I don't want
to have to drop packets that have already used up
bandwidth getting to the machine, and making matters
worse by requiring the packets to be sent again.
Thanks,
Casey
----- Original Message -----
From: Randy Grimshaw <rgrimsha@syr.edu>
To: netfilter@lists.netfilter.org, casey@phantombsd.org
Sent: Wednesday, April 5, 2006 10:27:48 AM GMT-0800
Subject: Re: Throttling NAT interface
Our throttle is really in the other direction but the
idea may work for you.
iptables [traffic pattern spec] -m limit --limit
40/second --limit-burst 60 -j LEVEL2
LEVEL2 is a user defined chain that specifies other
restrictions or in your case NAT translations.
The point is that you can match the traffic patterns
that you need before applying the limit match.
hope this is helpful.
<><Randy
<><Randall Grimshaw
Room 203 Machinery Hall
Syracuse University
Syracuse, NY 13244
315-443-5779
rgrimsha@syr.edu
>>> Casey Scott <casey@phantombsd.org> 4/5/2006 12:44 PM >>>
The gist of what I need to do is restrict the rate of
off-network traffic coming in through a host. The host
is providing basic NAT to an internal network. I have
gotten pretty close to what I need to do with iptables
and tc. The problem is that when an interface is throttle
with tc, the source of the traffic doesn't matter. I don't
want to throttle local traffic, just traffic coming through
the machine from a WAN. The next step was to add another
NIC to the machine. Something like this:
eth0: <local IP1>
eth1: <WAN IP>
eth2: <local IP2>
The problem is that even if traffic destined to be routed
off network comes into eth2, which is throttle via tc, the
return traffic comes back through eth0. Since tc (tbf filter)
just controls the transmitting of an interface, I need to
force the NAT traffic to use eth2. Traffic that is meant to
stay local can use eth0. Is possible to do something like this?
How can I this host to only eth2 for NAT even though both eth0
and eth2 are in the same network? eth0 is not throttled, which
is why local traffic needs to use it.
TIA,
Casey
^ permalink raw reply
* Re: [linux-usb-devel] compile error when building multiple EHCI host controllers as modules
From: Kumar Gala @ 2006-04-05 17:32 UTC (permalink / raw)
To: David Brownell; +Cc: linux-usb-devel, Greg KH, LKML mailing list
In-Reply-To: <074E7D37-773D-4203-BB09-20040C5D5D5B@kernel.crashing.org>
> Let me test this patch out. I'm ok with the changes for handling
> both PCI and platform driver. However, I need to take a look at the
> renaming of the fsl driver. The "dr" device supports device and OTG
> modes. I'm concerned about how we distinguish that in the future.
>
> (also, we need to fixup arch/powerpc/sysdev/fsl_soc.c)
Here's a cleaned up version that builds and fixes up some warnings for me.
I need to cleanup the code in arch/powerpc/sysdev/fsl_soc.c a bit, but it
works for now.
diff --git a/drivers/usb/host/ehci-au1xxx.c b/drivers/usb/host/ehci-au1xxx.c
index 63eadee..036a1c0 100644
--- a/drivers/usb/host/ehci-au1xxx.c
+++ b/drivers/usb/host/ehci-au1xxx.c
@@ -280,18 +280,3 @@ static struct device_driver ehci_hcd_au1
/*.suspend = ehci_hcd_au1xxx_drv_suspend, */
/*.resume = ehci_hcd_au1xxx_drv_resume, */
};
-
-static int __init ehci_hcd_au1xxx_init(void)
-{
- pr_debug(DRIVER_INFO " (Au1xxx)\n");
-
- return driver_register(&ehci_hcd_au1xxx_driver);
-}
-
-static void __exit ehci_hcd_au1xxx_cleanup(void)
-{
- driver_unregister(&ehci_hcd_au1xxx_driver);
-}
-
-module_init(ehci_hcd_au1xxx_init);
-module_exit(ehci_hcd_au1xxx_cleanup);
diff --git a/drivers/usb/host/ehci-fsl.c b/drivers/usb/host/ehci-fsl.c
index f985f12..30410c2 100644
--- a/drivers/usb/host/ehci-fsl.c
+++ b/drivers/usb/host/ehci-fsl.c
@@ -339,28 +339,3 @@ static struct platform_driver ehci_fsl_m
.name = "fsl-usb2-mph",
},
};
-
-static int __init ehci_fsl_init(void)
-{
- int retval;
-
- pr_debug("%s: block sizes: qh %Zd qtd %Zd itd %Zd sitd %Zd\n",
- hcd_name,
- sizeof(struct ehci_qh), sizeof(struct ehci_qtd),
- sizeof(struct ehci_itd), sizeof(struct ehci_sitd));
-
- retval = platform_driver_register(&ehci_fsl_dr_driver);
- if (retval)
- return retval;
-
- return platform_driver_register(&ehci_fsl_mph_driver);
-}
-
-static void __exit ehci_fsl_cleanup(void)
-{
- platform_driver_unregister(&ehci_fsl_mph_driver);
- platform_driver_unregister(&ehci_fsl_dr_driver);
-}
-
-module_init(ehci_fsl_init);
-module_exit(ehci_fsl_cleanup);
diff --git a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
index 79f2d8b..549ce59 100644
--- a/drivers/usb/host/ehci-hcd.c
+++ b/drivers/usb/host/ehci-hcd.c
@@ -905,3 +905,57 @@ MODULE_LICENSE ("GPL");
#ifndef EHCI_BUS_GLUED
#error "missing bus glue for ehci-hcd"
#endif
+
+static int __init ehci_hcd_init(void)
+{
+ int retval = 0;
+
+ pr_debug("%s: block sizes: qh %Zd qtd %Zd itd %Zd sitd %Zd\n",
+ hcd_name,
+ sizeof(struct ehci_qh), sizeof(struct ehci_qtd),
+ sizeof(struct ehci_itd), sizeof(struct ehci_sitd));
+
+#ifdef CONFIG_PPC_83xx
+ retval = platform_driver_register(&ehci_fsl_dr_driver);
+ if (retval < 0)
+ return retval;
+
+ retval = platform_driver_register(&ehci_fsl_dr_driver);
+ if (retval < 0)
+ return retval;
+#endif
+
+#ifdef CONFIG_SOC_AU1X00
+ pr_debug(DRIVER_INFO " (Au1xxx)\n");
+
+ retval = driver_register(&ehci_hcd_au1xxx_driver);
+ if (retval < 0)
+ return retval;
+#endif
+
+#ifdef CONFIG_PCI
+ retval = pci_register_driver(&ehci_pci_driver);
+ if (retval < 0)
+ return retval;
+#endif
+
+ return retval;
+}
+
+static void __exit ehci_hcd_cleanup(void)
+{
+#ifdef CONFIG_PPC_83xx
+ platform_driver_unregister(&ehci_fsl_mph_driver);
+ platform_driver_unregister(&ehci_fsl_dr_driver);
+#endif
+#ifdef CONFIG_SOC_AU1X00
+ driver_unregister(&ehci_hcd_au1xxx_driver);
+#endif
+#ifdef CONFIG_PCI
+ pci_unregister_driver(&ehci_pci_driver);
+#endif
+}
+
+module_init(ehci_hcd_init);
+module_exit(ehci_hcd_cleanup);
+
diff --git a/drivers/usb/host/ehci-pci.c b/drivers/usb/host/ehci-pci.c
index 1e03f1a..e0641bc 100644
--- a/drivers/usb/host/ehci-pci.c
+++ b/drivers/usb/host/ehci-pci.c
@@ -370,23 +370,3 @@ static struct pci_driver ehci_pci_driver
.resume = usb_hcd_pci_resume,
#endif
};
-
-static int __init ehci_hcd_pci_init(void)
-{
- if (usb_disabled())
- return -ENODEV;
-
- pr_debug("%s: block sizes: qh %Zd qtd %Zd itd %Zd sitd %Zd\n",
- hcd_name,
- sizeof(struct ehci_qh), sizeof(struct ehci_qtd),
- sizeof(struct ehci_itd), sizeof(struct ehci_sitd));
-
- return pci_register_driver(&ehci_pci_driver);
-}
-module_init(ehci_hcd_pci_init);
-
-static void __exit ehci_hcd_pci_cleanup(void)
-{
- pci_unregister_driver(&ehci_pci_driver);
-}
-module_exit(ehci_hcd_pci_cleanup);
^ permalink raw reply related
* [linux-lvm] pvmove to smaller PVs
From: Fredrik Tolf @ 2006-04-05 17:34 UTC (permalink / raw)
To: linux-lvm
I'm trying to use pvmove to move data from a 300 GB S-ATA disk onto
four, smaller 120 GB IDE disks. However, pvmove tells me that it cannot
allocate enough contiguous PEs to fit 300 GB, like this:
# pvmove /dev/sde1
Insufficient contiguous allocatable extents (28617) for logical volume
pvmove0: 71541 required
Unable to allocate temporary LV for pvmove.
I can, of course, understand that it can't find contiguous PEs
corresponding to 300 GB, but I don't understand why it should need it to
be contiguous. Can pvmove not just divide that storage into three
"partitions", each fitting on one 120 GB disk, and move them? Is there a
way for me to tell it to do so?
I seem to be able to use something like "pvmove /dev/sde1:0-28616" to
tell pvmove manually to do this for me, but this poses a small problem
for me, as not all of the data on the disks I want to move from are
allocated where I know them to be. This particular disk is fully
allocated, so that I know what I could do with that syntax, but is there
really no way to tell pvmove to do this automatically? It just seems
kind of strange to me.
Fredrik Tolf
^ permalink raw reply
* Re: Fix ia64 bit ops: Full barriers for bit operations returning a
From: Christoph Lameter @ 2006-04-05 17:31 UTC (permalink / raw)
To: linux-ia64
In-Reply-To: <Pine.LNX.4.64.0604031129510.21064@schroedinger.engr.sgi.com>
On Wed, 5 Apr 2006, Zoltan Menyhart wrote:
> Christoph Lameter wrote:
>
> > Could decomplicate this? Just use acquire / release and avoid the additional
> > intrinsics. The purpose is first of all correctness. Then we can add some
> > whiz bang on top. Also please sent patches inline not as attachments.
>
> I could have misunderstood what you wrote yesterday:
>
> > > Could you consider using some cache hints, like "ld8.bias.nta"?
> > > "bias" is a hint to acquire exclusive ownership.
> > > "nta" is a hint to allocate the cache line only in L2
> > > (and side effect: to bias it to be replaced).
> > > All of the Itanium 2 processor's atomic instructions are handled
> > > exclusively by the L2 cache.
> >
> > Could you come up with a patch? Currently, I do not seem to be able to spend
> > enough time on it.
>
> I thought you had asked for both the correct fencing and the cache hints.
Oh. Sorry.
The new patch seems to be okay but it still was not sent inline and is
therefore difficult to review for most of us.
^ permalink raw reply
* [2.6.17-rc1] ALSA oops with multiple OSS clients
From: Luca @ 2006-04-05 17:30 UTC (permalink / raw)
To: linux-kernel; +Cc: perex, alsa-devel
Hello,
I've a reproducible OOPS when starting multiple OSS clients.
To reproduce I do this:
mpg123 song.mp3
mpg123 song.mp3 (another time)
At this point the song restart from the beginning (i.e. I think that
the second mpg123 takes over the device). When the second instance
terminates the song I get the following OOPS:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00000260
printing eip:
f18df6e0
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: radeon drm lp cls_u32 cls_route sch_sfq sch_cbq nfsd
exportfs lockd sunrpc nls_iso8859_15 nls_cp850 vfat fat
nls_utf8 ntfs xfs reiserfs tcp_westwood w83627hf hwmon_vid i2c_isa ipv6
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx
snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device uhci_hcd rtc
snd usbcore i2c_viapro soundcore via_agp agpgart
CPU: 0
EIP: 0060:[<f18df6e0>] Not tainted VLI
EFLAGS: 00210286 (2.6.17-rc1 #5)
EIP is at snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss]
eax: efe804a0 ebx: 00000000 ecx: 00000000 edx: 0808f158
esi: 00002000 edi: efe804a0 ebp: 0808f158 esp: cc1ebf3c
ds: 007b es: 007b ss: 0068
Process mpg123 (pid: 4843, threadinfo=cc1ea000 task=e80e2530)
Stack: <0>00000000 0001e09c 00000000 b03f6a68 ea4e33a0 0808f0d8 b1a97800 00003f80
f18e0aa7 00000000 0808f158 efe804a0 00000080 ea4e33a0 0808f0d8 cc1ebfa4
00004000 b015aaa3 cc1ebfa4 f18e0930 ea4e33a0 fffffff7 00000003 cc1ea000
Call Trace:
<f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss] <b015aaa3> vfs_write+0xa3/0x160
<f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss] <b015b111> sys_write+0x41/0x70
<b010301f> syscall_call+0x7/0xb
Code: ff ff ff 5b 5e 5f 5d c3 8d 76 00 83 ec 20 89 74 24 14 89 7c 24 18
89 c7 89 6c 24 1c 89 5c 24 10 89 ce 8b 58 5c 89 d5 8b 4c 24 24 <8b> 83
60 02 00 00 85 c0 74 6e 8b 50 20 85 c9 89 54 24 04 8b 40
<1>BUG: unable to handle kernel NULL pointer dereference at virtual
address 000000a0
printing eip:
f18e1918
*pde = 00000000
Oops: 0000 [#2]
PREEMPT
Modules linked in: radeon drm lp cls_u32 cls_route sch_sfq sch_cbq nfsd
exportfs lockd sunrpc nls_iso8859_15 nls_cp850 vfat fat
nls_utf8 ntfs xfs reiserfs tcp_westwood w83627hf hwmon_vid i2c_isa ipv6
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx
snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device uhci_hcd rtc
snd usbcore i2c_viapro soundcore via_agp agpgart
CPU: 0
EIP: 0060:[<f18e1918>] Not tainted VLI
EFLAGS: 00210286 (2.6.17-rc1 #5)
EIP is at snd_pcm_oss_sync+0x18/0x240 [snd_pcm_oss]
eax: efe804a0 ebx: 00000008 ecx: f18e26f0 edx: ea4e33a0
esi: 00000000 edi: ef8ab000 ebp: cc1ebdc8 esp: cc1ebda0
ds: 007b es: 007b ss: 0068
Process mpg123 (pid: 4843, threadinfo=cc1ea000 task=e80e2530)
Stack: <0>ed85c800 00000000 0000059b de601900 efe804a0 7ffffa65 00000000 00000008
de601900 ef8ab000 ea4e33a0 f18e271b 00000008 00200246 cc1ea000 ef6011bc
00000008 ef667fb8 ef60109c ea4e33a0 b015b55a 00000000 ef667f60 effe3e20
Call Trace:
<f18e271b> snd_pcm_oss_release+0x2b/0x120 [snd_pcm_oss] <b015b55a> __fput+0xaa/0x1e0
<b0158687> filp_close+0x47/0x80 <b011c997> put_files_struct+0x97/0xc0
<b011ddb5> do_exit+0x145/0x970 <b0103a62> common_interrupt+0x1a/0x20
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18df6e0> snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss] <f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss]
<b015aaa3> vfs_write+0xa3/0x160 <f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss]
<b015b111> sys_write+0x41/0x70 <b010301f> syscall_call+0x7/0xb
Code: c7 42 14 f4 ff ff ff 8b 44 24 04 e8 23 05 a2 be eb 9a 90 55 89 e5
57 56 53 83 ec 1c 89 45 e4 8b 00 85 c0 89 45 e8 74 4d 8b 70 5c <8b> 86
a0 00 00 00 85 c0 0f 84 8a 00 00 00 8b 45 e8 31 c9 8b 90
<1>Fixing recursive fault but reboot is needed!
The first instance of mpg123 remains in D state:
mpg123 D B036A4B8 5560 4843 4833 (L-TLB)
cc1ebca4 c7b31920 00000002 b036a4b8 b03f81c0 cc1ea000 a2bac600 003d0c01
00000009 e80e2638 e80e2530 a2bac600 003d0c01 00000000 00000000 00000000
cc1ea000 06acfc00 00000000 cc1ea000 e80e2530 ffffffff 0000000b b011e53d
Call Trace:
<b011e53d> do_exit+0x8cd/0x970 <b0300480> preempt_schedule+0x50/0x70
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18e26f0> snd_pcm_oss_release+0x0/0x120 [snd_pcm_oss] <f18e1918> snd_pcm_oss_sync+0x18/0x240 [snd_pcm_oss]
<f18e271b> snd_pcm_oss_release+0x2b/0x120 [snd_pcm_oss] <b015b55a> __fput+0xaa/0x1e0
<b0158687> filp_close+0x47/0x80 <b011c997> put_files_struct+0x97/0xc0
<b011ddb5> do_exit+0x145/0x970 <b0103a62> common_interrupt+0x1a/0x20
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18df6e0> snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss] <f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss]
<b015aaa3> vfs_write+0xa3/0x160 <f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss]
<b015b111> sys_write+0x41/0x70 <b010301f> syscall_call+0x7/0xb
The default ALSA device (in case it matters) is dmix. mpg123 is the old
mpg123 (not mpg321) and it's using the OSS interface (emulated by ALSA).
The relevant portion of my .config:
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y <-- It may be related to this one?
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_DETECT=y
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
#
# PCI devices
#
CONFIG_SND_VIA82XX=m
Luca
--
Home: http://kronoz.cjb.net
La vasca da bagno fu inventata nel 1850, il telefono nel 1875.
Se fossi vissuto nel 1850, avrei potuto restare in vasca per 25 anni
seinza sentir squillare il telefono
^ permalink raw reply
* [2.6.17-rc1] ALSA oops with multiple OSS clients
From: Luca @ 2006-04-05 17:30 UTC (permalink / raw)
To: linux-kernel; +Cc: perex, alsa-devel
Hello,
I've a reproducible OOPS when starting multiple OSS clients.
To reproduce I do this:
mpg123 song.mp3
mpg123 song.mp3 (another time)
At this point the song restart from the beginning (i.e. I think that
the second mpg123 takes over the device). When the second instance
terminates the song I get the following OOPS:
BUG: unable to handle kernel NULL pointer dereference at virtual address
00000260
printing eip:
f18df6e0
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: radeon drm lp cls_u32 cls_route sch_sfq sch_cbq nfsd
exportfs lockd sunrpc nls_iso8859_15 nls_cp850 vfat fat
nls_utf8 ntfs xfs reiserfs tcp_westwood w83627hf hwmon_vid i2c_isa ipv6
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx
snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device uhci_hcd rtc
snd usbcore i2c_viapro soundcore via_agp agpgart
CPU: 0
EIP: 0060:[<f18df6e0>] Not tainted VLI
EFLAGS: 00210286 (2.6.17-rc1 #5)
EIP is at snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss]
eax: efe804a0 ebx: 00000000 ecx: 00000000 edx: 0808f158
esi: 00002000 edi: efe804a0 ebp: 0808f158 esp: cc1ebf3c
ds: 007b es: 007b ss: 0068
Process mpg123 (pid: 4843, threadinfo=cc1ea000 task=e80e2530)
Stack: <0>00000000 0001e09c 00000000 b03f6a68 ea4e33a0 0808f0d8 b1a97800 00003f80
f18e0aa7 00000000 0808f158 efe804a0 00000080 ea4e33a0 0808f0d8 cc1ebfa4
00004000 b015aaa3 cc1ebfa4 f18e0930 ea4e33a0 fffffff7 00000003 cc1ea000
Call Trace:
<f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss] <b015aaa3> vfs_write+0xa3/0x160
<f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss] <b015b111> sys_write+0x41/0x70
<b010301f> syscall_call+0x7/0xb
Code: ff ff ff 5b 5e 5f 5d c3 8d 76 00 83 ec 20 89 74 24 14 89 7c 24 18
89 c7 89 6c 24 1c 89 5c 24 10 89 ce 8b 58 5c 89 d5 8b 4c 24 24 <8b> 83
60 02 00 00 85 c0 74 6e 8b 50 20 85 c9 89 54 24 04 8b 40
<1>BUG: unable to handle kernel NULL pointer dereference at virtual
address 000000a0
printing eip:
f18e1918
*pde = 00000000
Oops: 0000 [#2]
PREEMPT
Modules linked in: radeon drm lp cls_u32 cls_route sch_sfq sch_cbq nfsd
exportfs lockd sunrpc nls_iso8859_15 nls_cp850 vfat fat
nls_utf8 ntfs xfs reiserfs tcp_westwood w83627hf hwmon_vid i2c_isa ipv6
snd_seq_oss snd_seq_midi snd_seq_midi_event snd_seq snd_via82xx
snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device uhci_hcd rtc
snd usbcore i2c_viapro soundcore via_agp agpgart
CPU: 0
EIP: 0060:[<f18e1918>] Not tainted VLI
EFLAGS: 00210286 (2.6.17-rc1 #5)
EIP is at snd_pcm_oss_sync+0x18/0x240 [snd_pcm_oss]
eax: efe804a0 ebx: 00000008 ecx: f18e26f0 edx: ea4e33a0
esi: 00000000 edi: ef8ab000 ebp: cc1ebdc8 esp: cc1ebda0
ds: 007b es: 007b ss: 0068
Process mpg123 (pid: 4843, threadinfo=cc1ea000 task=e80e2530)
Stack: <0>ed85c800 00000000 0000059b de601900 efe804a0 7ffffa65 00000000 00000008
de601900 ef8ab000 ea4e33a0 f18e271b 00000008 00200246 cc1ea000 ef6011bc
00000008 ef667fb8 ef60109c ea4e33a0 b015b55a 00000000 ef667f60 effe3e20
Call Trace:
<f18e271b> snd_pcm_oss_release+0x2b/0x120 [snd_pcm_oss] <b015b55a> __fput+0xaa/0x1e0
<b0158687> filp_close+0x47/0x80 <b011c997> put_files_struct+0x97/0xc0
<b011ddb5> do_exit+0x145/0x970 <b0103a62> common_interrupt+0x1a/0x20
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18df6e0> snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss] <f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss]
<b015aaa3> vfs_write+0xa3/0x160 <f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss]
<b015b111> sys_write+0x41/0x70 <b010301f> syscall_call+0x7/0xb
Code: c7 42 14 f4 ff ff ff 8b 44 24 04 e8 23 05 a2 be eb 9a 90 55 89 e5
57 56 53 83 ec 1c 89 45 e4 8b 00 85 c0 89 45 e8 74 4d 8b 70 5c <8b> 86
a0 00 00 00 85 c0 0f 84 8a 00 00 00 8b 45 e8 31 c9 8b 90
<1>Fixing recursive fault but reboot is needed!
The first instance of mpg123 remains in D state:
mpg123 D B036A4B8 5560 4843 4833 (L-TLB)
cc1ebca4 c7b31920 00000002 b036a4b8 b03f81c0 cc1ea000 a2bac600 003d0c01
00000009 e80e2638 e80e2530 a2bac600 003d0c01 00000000 00000000 00000000
cc1ea000 06acfc00 00000000 cc1ea000 e80e2530 ffffffff 0000000b b011e53d
Call Trace:
<b011e53d> do_exit+0x8cd/0x970 <b0300480> preempt_schedule+0x50/0x70
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18e26f0> snd_pcm_oss_release+0x0/0x120 [snd_pcm_oss] <f18e1918> snd_pcm_oss_sync+0x18/0x240 [snd_pcm_oss]
<f18e271b> snd_pcm_oss_release+0x2b/0x120 [snd_pcm_oss] <b015b55a> __fput+0xaa/0x1e0
<b0158687> filp_close+0x47/0x80 <b011c997> put_files_struct+0x97/0xc0
<b011ddb5> do_exit+0x145/0x970 <b0103a62> common_interrupt+0x1a/0x20
<b0104586> die+0x266/0x270 <b011524e> do_page_fault+0x29e/0x6ae
<b0114fb0> do_page_fault+0x0/0x6ae <b0103b2b> error_code+0x4f/0x54
<f18df6e0> snd_pcm_oss_write2+0x20/0xf0 [snd_pcm_oss] <f18e0aa7> snd_pcm_oss_write+0x177/0x1e0 [snd_pcm_oss]
<b015aaa3> vfs_write+0xa3/0x160 <f18e0930> snd_pcm_oss_write+0x0/0x1e0 [snd_pcm_oss]
<b015b111> sys_write+0x41/0x70 <b010301f> syscall_call+0x7/0xb
The default ALSA device (in case it matters) is dmix. mpg123 is the old
mpg123 (not mpg321) and it's using the OSS interface (emulated by ALSA).
The relevant portion of my .config:
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y <-- It may be related to this one?
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
# CONFIG_SND_SUPPORT_OLD_API is not set
# CONFIG_SND_VERBOSE_PROCFS is not set
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_DETECT=y
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
#
# PCI devices
#
CONFIG_SND_VIA82XX=m
Luca
--
Home: http://kronoz.cjb.net
La vasca da bagno fu inventata nel 1850, il telefono nel 1875.
Se fossi vissuto nel 1850, avrei potuto restare in vasca per 25 anni
seinza sentir squillare il telefono
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply
* Re: [PATCH] crypto: fix unaligned access in khazad module
From: Herbert Xu @ 2006-04-05 17:29 UTC (permalink / raw)
To: Atsushi Nemoto; +Cc: linux-kernel, linux-crypto, akpm
In-Reply-To: <20060404.165552.52129978.nemoto@toshiba-tops.co.jp>
On Tue, Apr 04, 2006 at 04:55:52PM +0900, Atsushi Nemoto wrote:
>
> On 64-bit platform, reading 64-bit keys (which is supposed to be
> 32-bit aligned) at a time will result in unaligned access.
Patch applied. Thanks a lot.
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
^ permalink raw reply
* Re: [uml-devel] system call accessing the host os
From: D. Bahi @ 2006-04-05 17:28 UTC (permalink / raw)
To: Olivier Crameri; +Cc: user-mode-linux-devel
In-Reply-To: <69927A9D-E6B1-4BD9-A51C-8B71960DBDDC@epfl.ch>
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
well there are several examples of this in the arch/um/drivers area.
<blah>_user.c and <blah>_kern.c break out the userspace and
kernel space parts of UML's dual personality.
Olivier Crameri wrote:
> Well, yes, I could use this.
>
> But what I'm actually trying to understand is how to properly execute
> regular C within the UML kernel to access the host OS.
>
> Thks,
>
> Olivier
>
> On 5 avr. 06, at 19:18, D. Bahi wrote:
>
>> what about this?
>>
>> http://user-mode-linux.sourceforge.net/iomem.html
>>
>> Olivier Crameri wrote:
>>> Hi,
>>>
>>> I'm currently working on a project in which we are using UML to access
>>> the host os and perform some operations.
>>> More precisely, we would like to have a system call in UML that parses
>>> a file in the host os.
>>>
>>> Since the UML kernel is a host process, I naively thought that I could
>>> use regular C directly. Indeed, I was able to create my system call,
>>> and then have some other C files compiled using host os headers such
>>> as <stdio.h> and <stdlib.h> by putting them in the USER_OBJS list of
>>> the Makefile.
>>>
>>> Unfortunately, I'm having some weird issues that I can't really
>>> understand. I can read the file using fread, but only in a buffer that
>>> I allocated using um_kmalloc. If I use a buffer allocated by malloc,
>>> the fread fails. Then, even if I replace all my mallocs by
>>> um_kmallocs, some libc functions (such as sscanf) don't seem to work
>>> properly. I guess I'm missing something, but I can't figure out what.
>>>
>>> If anyone of you can help me, I'd really appreciate,
>>>
>>> With best regards,
>>>
>>> Olivier
>>>
>>> P.S.: I'm using 2.6.15.6 with the latest 2.6.15 patch and the guest
>>> kernel runs in skas3 mode.
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>> language
>>> that extends applications into web and mobile media. Attend the live
>>> webcast
>>> and join the prime developer group breaking into this new coding
>>> territory!
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>
>>> _______________________________________________
>>> User-mode-linux-devel mailing list
>>> User-mode-linux-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
^ permalink raw reply
* Re: Throttling NAT interface
From: Randy Grimshaw @ 2006-04-05 17:27 UTC (permalink / raw)
To: netfilter, casey
Our throttle is really in the other direction but the idea may work for you.
iptables [traffic pattern spec] -m limit --limit 40/second --limit-burst 60 -j LEVEL2
LEVEL2 is a user defined chain that specifies other restrictions or in your case NAT translations. The point is that you can match the traffic patterns that you need before applying the limit match.
hope this is helpful.
<><Randy
<><Randall Grimshaw
Room 203 Machinery Hall
Syracuse University
Syracuse, NY 13244
315-443-5779
rgrimsha@syr.edu
>>> Casey Scott <casey@phantombsd.org> 4/5/2006 12:44 PM >>>
The gist of what I need to do is restrict the rate of
off-network traffic coming in through a host. The host
is providing basic NAT to an internal network. I have
gotten pretty close to what I need to do with iptables
and tc. The problem is that when an interface is throttle
with tc, the source of the traffic doesn't matter. I don't
want to throttle local traffic, just traffic coming through
the machine from a WAN. The next step was to add another
NIC to the machine. Something like this:
eth0: <local IP1>
eth1: <WAN IP>
eth2: <local IP2>
The problem is that even if traffic destined to be routed
off network comes into eth2, which is throttle via tc, the
return traffic comes back through eth0. Since tc (tbf filter)
just controls the transmitting of an interface, I need to
force the NAT traffic to use eth2. Traffic that is meant to
stay local can use eth0. Is possible to do something like this?
How can I this host to only eth2 for NAT even though both eth0
and eth2 are in the same network? eth0 is not throttled, which
is why local traffic needs to use it.
TIA,
Casey
^ permalink raw reply
* Re: FAQ entry for loopback mounting
From: David Woodhouse @ 2006-04-05 17:27 UTC (permalink / raw)
To: Ralph Siemsen; +Cc: linux-mtd
In-Reply-To: <4433F9FE.7020501@rossvideo.com>
On Wed, 2006-04-05 at 13:10 -0400, Ralph Siemsen wrote:
> I misread the code a bit. "Mi" and "Gi" should in fact work (I didn't
> try them), having been bitten repeatedly by neither "k" or "kB" working
> as one might have (naviely) expected. Yes I know the "i" thing is SI
> standard but the old "be leniant in what you accept" policy really
> should apply imho.
We _are_ being lenient. If you say 'k' or 'M' instead of 'Ki' or 'Mi'
then you are going to get the powers of ten which you asked for... which
is almost certainly _not_ what you wanted. Giving you powers of two is
not an option. So it's best not to accept it at all.
--
dwmw2
^ permalink raw reply
* Re: [patch 03/26] sysfs: zero terminate sysfs write buffers (CVE-2006-1055)
From: Al Viro @ 2006-04-05 17:27 UTC (permalink / raw)
To: Jon Smirl; +Cc: gregkh, linux-kernel, stable
In-Reply-To: <9e4733910604051006q447ec3absec038732c5a7a9f2@mail.gmail.com>
On Wed, Apr 05, 2006 at 01:06:32PM -0400, Jon Smirl wrote:
> On 4/5/06, Al Viro <viro@ftp.linux.org.uk> wrote:
> > On Wed, Apr 05, 2006 at 12:34:49PM -0400, Jon Smirl wrote:
> > > On 4/5/06, Al Viro <viro@ftp.linux.org.uk> wrote:
> > > > On Wed, Apr 05, 2006 at 07:09:28PM +0400, Sergey Vlasov wrote:
> > > > > This will break the "color_map" sysfs file for framebuffers -
> > > > > drivers/video/fbsysfs.c:store_cmap() expects to get exactly 4096 bytes
> > > > > for a colormap with 256 entries. In fact, the original patch which
> > > > > changed PAGE_SIZE - 1 to PAGE_SIZE:
> > > >
> > > > ... cheerfully assuming that nobody assumes NUL-termination and
> > > > everyone (sysfs patch writers!) certainly uses the length argument.
> > > > Fscking brilliant, that.
> > >
> > > Why does sysfs have two string length determination methods - both
> > > NULL termination and a length parameter. It should be one or the
> > > other, not both. Having both simply cause problems when some
> > > developers implement one scheme and others only implement the other.
> >
> > Which part of "sysfs patches can be written by idiots and usually are"
> > is too hard to understand? Oh, wait. I see... Well, nevermind, then...
>
> I look forward to seeing your patches address these problems.
I don't patch wetware. As for the NUL-termination, fixing widespread breakage
you've introduced is _your_ responsibility. Preferably taken care of before
submitting the patch in question. As far as I'm concerned, reverting it
solves the problem.
I'm sorry, but by now I'm _REALLY_ sick and tired of sysfs wankers crowd
and your brand of idiocy is getting slightly past the annoying stage.
Let me spell it out for you:
1) when you change the property of implementation, you must at least
try to check how much might rely on it.
2) when interface is not documented, do not assume that its properties
are accidental and/or not relied upon.
3) if you are breaking things, at least make sure that breakage is
easily found. Do not introduce an obscure case when old assumption is false;
make it visible.
4) when considerable part of interface users is obviously broken
by a change and you want to preserve that change, suggesting that somebody
else should fix the interface users for you since they did not match your
assumptions is... not the brightest idea in the world.
^ permalink raw reply
* Re: Can't mount /dev/md0 after stopping a synchronization
From: Paul Clements @ 2006-04-05 17:24 UTC (permalink / raw)
To: Mike Garey; +Cc: linux-raid
In-Reply-To: <c79e949d0604050839k2287fefdm53f6abb08dfcae89@mail.gmail.com>
Mike Garey wrote:
> I seem to be getting closer.. If I try booting from a kernel without
> raid1 and md support, but using an initrd with raid1/md modules, then
> I get the "ALERT! /dev/md0 does not exist. Dropping to a shell!"
> message. I can't understand why there would be any difference between
> using a kernel with raid1/md support, or using an initrd image with
> raid1/md support, but apparently there is. If anyone else has any
Autodetection doesn't occur unless md is built into the kernel -- one of
the reasons why using autodetection is becoming less and less popular.
You're probably better off assembling the array from your initrd with
some invocation of mdadm.
--
Paul
^ permalink raw reply
* Re: [uml-devel] system call accessing the host os
From: Olivier Crameri @ 2006-04-05 17:24 UTC (permalink / raw)
To: user-mode-linux-devel
In-Reply-To: <946EDC7F-5F36-4453-93E8-36BBC8D9F032@epfl.ch>
Well, yes, I could use this.
But what I'm actually trying to understand is how to properly execute
regular C within the UML kernel to access the host OS.
Thks,
Olivier
On 5 avr. 06, at 19:18, D. Bahi wrote:
> what about this?
>
> http://user-mode-linux.sourceforge.net/iomem.html
>
> Olivier Crameri wrote:
>> Hi,
>>
>> I'm currently working on a project in which we are using UML to
>> access
>> the host os and perform some operations.
>> More precisely, we would like to have a system call in UML that
>> parses
>> a file in the host os.
>>
>> Since the UML kernel is a host process, I naively thought that I
>> could
>> use regular C directly. Indeed, I was able to create my system call,
>> and then have some other C files compiled using host os headers such
>> as <stdio.h> and <stdlib.h> by putting them in the USER_OBJS list of
>> the Makefile.
>>
>> Unfortunately, I'm having some weird issues that I can't really
>> understand. I can read the file using fread, but only in a buffer
>> that
>> I allocated using um_kmalloc. If I use a buffer allocated by malloc,
>> the fread fails. Then, even if I replace all my mallocs by
>> um_kmallocs, some libc functions (such as sscanf) don't seem to work
>> properly. I guess I'm missing something, but I can't figure out what.
>>
>> If anyone of you can help me, I'd really appreciate,
>>
>> With best regards,
>>
>> Olivier
>>
>> P.S.: I'm using 2.6.15.6 with the latest 2.6.15 patch and the guest
>> kernel runs in skas3 mode.
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>> language
>> that extends applications into web and mobile media. Attend the live
>> webcast
>> and join the prime developer group breaking into this new coding
>> territory!
>> http://sel.as-us.falkag.net/sel?
>> cmd=lnk&kid=110944&bid=241720&dat=121642
>> _______________________________________________
>> User-mode-linux-devel mailing list
>> User-mode-linux-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: help? converting to single global prio_array in scheduler, ran into snag
From: Christopher Friesen @ 2006-04-05 17:23 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <4433F636.3090705@nortel.com>
I should clarify that CKRM is currently disabled--I'm trying to get the
vanilla scheduler working first before changing the CKRM stuff to use
per-class prio arrays rather than per-class per-cpu ones.
Chris
^ permalink raw reply
* ip6tables flow diagram
From: Undertacker @ 2006-04-05 17:22 UTC (permalink / raw)
To: netfilter
Dear All
I’m trying to configure my ip6tables. To understand better how it’s work
I need a ip6tablesa flow scheme. I try to search it on google but
without success.
Can you please tell me if you haw or know where to fine an flow diagram?
Best Regards
Under
^ permalink raw reply
* Re: [2.6 patch] drivers/char/random.c: unexport secure_ipv6_port_ephemeral
From: Adrian Bunk @ 2006-04-05 17:19 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: mpm, linux-kernel, netdev
In-Reply-To: <20060405101111.0edc161a@localhost.localdomain>
On Wed, Apr 05, 2006 at 10:11:11AM -0700, Stephen Hemminger wrote:
> On Wed, 5 Apr 2006 18:36:10 +0200
> Adrian Bunk <bunk@stusta.de> wrote:
>
> > This patch removes the unused EXPORT_SYMBOL(secure_ipv6_port_ephemeral).
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > --- linux-2.6.17-rc1-mm1-full/drivers/char/random.c.old 2006-04-05 17:00:04.000000000 +0200
> > +++ linux-2.6.17-rc1-mm1-full/drivers/char/random.c 2006-04-05 17:00:22.000000000 +0200
> > @@ -1584,7 +1584,6 @@
> >
> > return twothirdsMD4Transform(daddr, hash);
> > }
> > -EXPORT_SYMBOL(secure_ipv6_port_ephemeral);
> > #endif
> >
> > #if defined(CONFIG_IP_DCCP) || defined(CONFIG_IP_DCCP_MODULE)
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe netdev" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> NAK
>
> If IPV6 is built as a module, then it is needed.
No, it isn't:
obj-$(subst m,y,$(CONFIG_IPV6)) += inet6_hashtables.o
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply
* Re: [uml-devel] system call accessing the host os
From: D. Bahi @ 2006-04-05 17:18 UTC (permalink / raw)
To: Olivier Crameri; +Cc: user-mode-linux-devel
In-Reply-To: <8F963598-0F1A-464A-991A-2FE95F9B418C@epfl.ch>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
what about this?
http://user-mode-linux.sourceforge.net/iomem.html
Olivier Crameri wrote:
> Hi,
>
> I'm currently working on a project in which we are using UML to access
> the host os and perform some operations.
> More precisely, we would like to have a system call in UML that parses
> a file in the host os.
>
> Since the UML kernel is a host process, I naively thought that I could
> use regular C directly. Indeed, I was able to create my system call,
> and then have some other C files compiled using host os headers such
> as <stdio.h> and <stdlib.h> by putting them in the USER_OBJS list of
> the Makefile.
>
> Unfortunately, I'm having some weird issues that I can't really
> understand. I can read the file using fread, but only in a buffer that
> I allocated using um_kmalloc. If I use a buffer allocated by malloc,
> the fread fails. Then, even if I replace all my mallocs by
> um_kmallocs, some libc functions (such as sscanf) don't seem to work
> properly. I guess I'm missing something, but I can't figure out what.
>
> If anyone of you can help me, I'd really appreciate,
>
> With best regards,
>
> Olivier
>
> P.S.: I'm using 2.6.15.6 with the latest 2.6.15 patch and the guest
> kernel runs in skas3 mode.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
^ permalink raw reply
* Re: bad tcp checksum
From: Jan den Ouden @ 2006-04-05 17:18 UTC (permalink / raw)
To: Tom Eastep; +Cc: netfilter
In-Reply-To: <200604050920.31151.teastep@shorewall.net>
Yes, you're right, the solution is the use ethtool in the domU domain to
disable checksum offloading. I didn't expect it was related to Xen, so
that's why I asked here.
Thanks for the pointer.
Jan
Tom Eastep wrote:
> On Wednesday 05 April 2006 08:51, Jan den Ouden (ml) wrote:
>
>> Hi,
>>
>> I'm seeing a strange problem with kernel 2.6.12 Xen domain0 with all
>> netfilter options compiled in. I'm trying to do port forwarding to an
>> internal machine from an internet gateway box.
>>
>> What works ok is forwarding from gateway:143 to internalmachine:143.
>>
>> But when I forward from gateway:1000 to internalmachine:143 I get bad
>> TCP checksums on the return packets. These packets are ignored on the
>> client machine on the external internet.
>>
>>
>
> I suggest that you search the Xen-users list archives -- this issue has been
> discussed ad nauseum.
>
> -Tom
>
^ permalink raw reply
* RE: Compiling xenoprof
From: Santos, Jose Renato G @ 2006-04-05 17:18 UTC (permalink / raw)
To: David Carr; +Cc: xen-devel
>> -----Original Message-----
>> From: David Carr [mailto:dc@dcarr.org]
>> Sent: Wednesday, April 05, 2006 10:10 AM
>> To: Santos, Jose Renato G; xen-devel@lists.xensource.com
>> Subject: Re: [Xen-devel] Compiling xenoprof
>>
>> Renato,
>>
>> I should have been more specific. The sequence of commands
>> from the guide that I use is below:
>>
>> On dom0:
>> [start guests]
>> opcontrol --reset
>>
>> opcontrol --no-vmlinux
>>
>> xm list
>> Name ID Mem(MiB) VCPUs State Time(s)
>> Domain-0 0 256 1 r----- 242.4
>> guest_0 11 128 1 -b---- 11.7
>> guest_1 12 128 1 -b---- 11.8
>>
>> sudo opcontrol --start-daemon --active-domains=guest_0,guest_1
>>
You should use domain ids and not domain names, i.e
--active-domains=11,12
I think it would be nice to have support for using domain names, but
It is not supported yet
Renato
^ permalink raw reply
* [uml-devel] system call accessing the host os
From: Olivier Crameri @ 2006-04-05 17:16 UTC (permalink / raw)
To: user-mode-linux-devel
Hi,
I'm currently working on a project in which we are using UML to
access the host os and perform some operations.
More precisely, we would like to have a system call in UML that
parses a file in the host os.
Since the UML kernel is a host process, I naively thought that I
could use regular C directly. Indeed, I was able to create my system
call, and then have some other C files compiled using host os headers
such as <stdio.h> and <stdlib.h> by putting them in the USER_OBJS
list of the Makefile.
Unfortunately, I'm having some weird issues that I can't really
understand. I can read the file using fread, but only in a buffer
that I allocated using um_kmalloc. If I use a buffer allocated by
malloc, the fread fails. Then, even if I replace all my mallocs by
um_kmallocs, some libc functions (such as sscanf) don't seem to work
properly. I guess I'm missing something, but I can't figure out what.
If anyone of you can help me, I'd really appreciate,
With best regards,
Olivier
P.S.: I'm using 2.6.15.6 with the latest 2.6.15 patch and the guest
kernel runs in skas3 mode.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply
* Re: [2.6 patch] drivers/char/random.c: unexport secure_ipv6_port_ephemeral
From: Stephen Hemminger @ 2006-04-05 17:11 UTC (permalink / raw)
To: Adrian Bunk; +Cc: mpm, linux-kernel, netdev
In-Reply-To: <20060405163610.GG8673@stusta.de>
On Wed, 5 Apr 2006 18:36:10 +0200
Adrian Bunk <bunk@stusta.de> wrote:
> This patch removes the unused EXPORT_SYMBOL(secure_ipv6_port_ephemeral).
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6.17-rc1-mm1-full/drivers/char/random.c.old 2006-04-05 17:00:04.000000000 +0200
> +++ linux-2.6.17-rc1-mm1-full/drivers/char/random.c 2006-04-05 17:00:22.000000000 +0200
> @@ -1584,7 +1584,6 @@
>
> return twothirdsMD4Transform(daddr, hash);
> }
> -EXPORT_SYMBOL(secure_ipv6_port_ephemeral);
> #endif
>
> #if defined(CONFIG_IP_DCCP) || defined(CONFIG_IP_DCCP_MODULE)
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
NAK
If IPV6 is built as a module, then it is needed.
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.