Am Montag, den 16.04.2007, 12:25 -0400 schrieb Michael Krufky:
> CIJOML wrote:
> > Dne pondělí 16 duben 2007 17:34 Michael Krufky napsal(a):
> >
> >> Adrian Bunk wrote:
> >>
> >>> On Sun, Apr 15, 2007 at 08:33:38PM -0400, Michael Krufky wrote:
> >>>
> Mauro,
>
> I've b
17 Nis 2007 Sal tarihinde, Ingo Molnar şunları yazmıştı:
> - fixed child-runs first. A /proc/sys/kernel/sched_child_runs_first
>flag can be used to turn it on/off. (This might fix the Kaffeine bug
>reported by S.Çağlar Onur <)
Sorry for delayed response but i just find some free time, do
From: Sebastian Kuzminsky <[EMAIL PROTECTED]>
Date: Mon, 16 Apr 2007 15:45:19 -0600
> I'm seeing some weird behavior in TCP. The issue is perfectly
> reproducible using netcat and other programs. This is what I do:
Please send your bug report again, but this time to the
[EMAIL PROTECTED] mailin
On Mon, Apr 16, 2007 at 11:00:01PM +0100, Alan Cox wrote:
> > don't actually have to care --- if loading an invalid profile can bring
> > down
> > the system, then that's no worse than an arbitrary module that crashes the
> > machine. Not sure if there will ever be user loadable profiles; at lea
From: Andrew Vasquez <[EMAIL PROTECTED]>
Date: Mon, 16 Apr 2007 14:10:49 -0700
> Ok, how about the following patch based on the one you posted which
> adds the codes to retrieve the WWPN/WWNN from firmware on SPARC, and
> also adds the module-parameter override I mentioned above.
>
> Perhaps the
this is the second release of the CFS (Completely Fair Scheduler)
patchset, against v2.6.21-rc7:
http://redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.patch
i'd like to thank everyone for the tremendous amount of feedback and
testing the v1 patch got - i could hardly keep up with just reading
Hugh Dickins wrote:
You're right to want to defer your pte_updates, David is right to want
to batch his TLB flushes. It bothers me that you have a surprising case,
and that unless you abandon your optimization, it imposes a new constraint
on how to proceed in common code (without #ifdef'ing arou
* Tony Lindgren <[EMAIL PROTECTED]> [070409 21:23]:
> From: Hiroshi DOYU <[EMAIL PROTECTED]>
>
> This patch adds a generic mailbox interface for for DSP and IVA
> (Image Video Accelerator). This patch itself doesn't contain
> any IVA driver.
Here's an updated version that merges in two later fixe
> don't actually have to care --- if loading an invalid profile can bring down
> the system, then that's no worse than an arbitrary module that crashes the
> machine. Not sure if there will ever be user loadable profiles; at least at
> that point we had to care.
CAP_SYS_RAWIO is needed to do ar
> > That is a fairly significant and sudden change to the existing
> > kernel/user interface.
>
> Well, this is not meant for 2.6.21. I hope it is possible to change it in
> early 2.6.22; otherwise if we can't fix mistakes from the past we are pretty
> doomed.
I don't believe the existing behav
On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> Hi Mauro,
>
> On 4/15/07, Mauro Carvalho Chehab <[EMAIL PROTECTED]> wrote:
> > - Fix Kernel Bugzilla #8301: spinlock fix for flexcop-pci
>
> While move of spin_lock_init before request_irq is obviously correct I
> wonder what is the reason behind chan
Adrian Bunk wrote:
> This email lists some known regressions in Linus' tree compared to 2.6.20.
>
> Subject: snd_intel8x0: divide error:
> References : http://lkml.org/lkml/2007/3/5/252
> Submitter : Michal Piotrowski <[EMAIL PROTECTED]>
> Status : unknown
>
Oops is in sound/pci/i
On Tue, Apr 17, 2007 at 12:28:31AM +0300, Mikko Tiihonen wrote:
> I actually was more worried that someone might complain that the pci
> scanning is copy & paste code from end of the same file. I did try to use
> the generic pci functions first but because they insist on enabling
> interrupts th
On Thu, Apr 12, 2007 at 11:21:01AM +0100, Alan Cox wrote:
> > +
> > + /**
> > +* parent can ptrace child when
> > +* - parent is unconfined
> > +* - parent is in complain mode
> > +* - parent and child are confined by the same profile
> > +*/
>
> Your profiles are name based.
On Tue, Apr 17, 2007 at 01:08:29AM +0400, Anton Vorontsov wrote:
> On Mon, Apr 16, 2007 at 09:24:21PM +0100, Russell King wrote:
> > Utterly unsafe. What happens if some other module gets loaded which
> > does this, and then this module is unloaded followed by the other
> > module. Result: Oops.
Hello Russell,
Monday, April 16, 2007, 11:24:21 PM, you wrote:
> On Fri, Apr 13, 2007 at 05:50:43PM +0400, Anton Vorontsov wrote:
>> +static void (*old_apm_get_power_status)(struct apm_power_info*);
>> +
>> +static int __init apm_battery_init(void)
>> +{
>> + printk(KERN_INFO "APM Battery Dri
Here we present our direct responses to the most frequent questions from
the AppArmor from the 2006 post.
Use of Pathnames For Access Control
---
Some people in the security field believe that pathnames are an
inappropriate security mechanism. This depends on what
On 4/16/07, Anton Vorontsov <[EMAIL PROTECTED]> wrote:
On Mon, Apr 16, 2007 at 12:14:27PM -0700, Matt Reimer wrote:
> The shifts (<< 3 and >> 5) are just to get the bits reassembled in the
> right positions. The multiplication by 5 and subtracting 1/8 is
> because (AFAIK) we can't do floating
On Mon, 16 Apr 2007, Andi Kleen wrote:
Mikko Tiihonen <[EMAIL PROTECTED]> writes:
It looks probable that most NVidia chipsets have the HPET address at
0x44. It might be possible to enable the HPET even if BIOS did not
That seems like a dangerous assumption. If anything this needs to be key
On Monday, 16 April 2007 11:50, Gautham Shenoy wrote:
> Hi Rafael,
>
> On 4/15/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > As I said before, we have a problem with using the CPU hotplug for
> > suspending
> > because of the notifiers that are called from within cpu_up()/cpu_d
On Monday, 16 April 2007 09:05, Pavel Machek wrote:
> Hi!
>
> > As I said before, we have a problem with using the CPU hotplug for
> > suspending
> > because of the notifiers that are called from within cpu_up()/cpu_down() and
> > (sometimes) assume that the system is fully functional.
> >
> > O
> actually, i designed the CFS code assuming a per-CPU TSC (with no global
> synchronization), not assuming any globally sync TSC. In fact i wrote it
That already worked in the old scheduler (just in a hackish way)
> on such systems: a CoreDuo2 box that has stops the TSC in C3 and the
> differ
Linus, please pull from
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This tree is also available from kernel.org mirrors at:
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
for-linus
This will get a one-liner that fixes data corruption
Il Sun, Apr 15, 2007 at 06:57:02PM -0600, Bjorn Helgaas ha scritto:
> On Sunday 15 April 2007 14:59, Luca Tettamanti wrote:
> > On 4/15/07, Bjorn Helgaas <[EMAIL PROTECTED]> wrote:
> > > But I missed the details, such as the specific devices in question,
> > > which ports they use, how they are de
John <[EMAIL PROTECTED]> writes:
Please use a full real name for posting.
> AFAIU, even a hard real-time OS is "defenseless" against SMIs that
> kick the CPU into SMM.
There are usually chipset specific bits that can be set to disable SMMs.
See the datasheet if you can get them. Unfortunately mo
On Mon, Apr 16, 2007 at 09:24:21PM +0100, Russell King wrote:
> On Fri, Apr 13, 2007 at 05:50:43PM +0400, Anton Vorontsov wrote:
> > +static void (*old_apm_get_power_status)(struct apm_power_info*);
> > +
> > +static int __init apm_battery_init(void)
> > +{
> > + printk(KERN_INFO "APM Battery Dri
On Mon, 16 Apr 2007, Andrew Vasquez wrote:
> On Mon, 16 Apr 2007, David Miller wrote:
>
> > They DON'T
> > CARE, they want their systems to work and if you don't give them that
> > you're not being a good driver maintainer.
>
> Let's push aside attitudes and unrealistic statistics, could we
> pe
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > i'm pleased to announce the first release of the "Modular Scheduler
> > Core and Completely Fair Scheduler [CFS]" patchset:
> >
> >http://redhat.com/~mingo/cfs-scheduler/sched-modular+cfs.patch
>
> I would suggest to drop the tsc.c change. The "s
On Thu, Apr 12, 2007 at 03:57:48PM -0700, Jeremy Fitzhardinge wrote:
> diff -r 2ad8a0729f26 arch/arm/boot/compressed/misc.c
> --- a/arch/arm/boot/compressed/misc.c Thu Apr 12 13:44:02 2007 -0700
> +++ b/arch/arm/boot/compressed/misc.c Thu Apr 12 15:48:43 2007 -0700
> @@ -239,7 +239,7 @@ static ulg
Hi -
On Mon, Apr 16, 2007 at 11:36:05PM +0200, Andi Kleen wrote:
> Christoph Hellwig <[EMAIL PROTECTED]> writes:
> > and [systemtap] does a lot of really wrong things in it's
> > runtime). [...]
(Thanks, Christoph, for at least a few specifics. Some of them have
already been dealt with in the re
On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> > > What about 4:
> > >
> > > When registering an [k]object increment refcount of module that
> > > provides ->release() function.
> > >
> > > That would normally require ->release function to be placed on
> > > subsystem level to allow unloading i
Ingo Molnar <[EMAIL PROTECTED]> writes:
> [announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
>
> i'm pleased to announce the first release of the "Modular Scheduler Core
> and Completely Fair Scheduler [CFS]" patchset:
>
>http://redhat.com/~mingo/cfs-scheduler/sche
This patch adds support for mail and wifi leds. It modifies the Kconfig
file to automatically pull led_class with wistron_btns, hopefully
everyone is fine with this.
Eric
From: Eric Piel <[EMAIL PROTECTED]>
wriston_btns: Add led support
Add support to wistron_btns for leds that comes with the
On Mon, Apr 16, 2007 at 08:27:08AM +0200, Andi Kleen wrote:
> > It's nice to check for consistency though, so we're adding that. Profile
> > loading is a trusted operation, at least so far, and so security wise we
> > don't actually have to care --- if loading an invalid profile can bring
> > do
On Mon, Apr 16, 2007 at 09:16:15PM +0100, Russell King wrote:
> On Fri, Apr 13, 2007 at 05:50:01PM +0400, Anton Vorontsov wrote:
> > +/*
> > + * include/linux/ioport.h does not provide flags for generic IRQ trigger
> > + * types. So, we're using "ISA PnP IRQ specific bits", and converting them.
> >
On Mon, Apr 16, 2007 at 03:38:52PM -0400, Alan Stern wrote:
> 3. Change the module code so that rmmod can return _before_ the
> module is actually unloaded from memory (but after the module's
> exit routine has completed). This will lead to more problems.
> For example, what
Christoph Hellwig <[EMAIL PROTECTED]> writes:
> and does a lot of really wrong things in it's runtime).
I must agree with that. Perhaps it would be good if its runtime code
was posted to l-k at some point and reviewed in the standard way
even when it isn't merged.
-Andi
-
To unsubscribe from thi
On Fri, Apr 13, 2007 at 05:50:43PM +0400, Anton Vorontsov wrote:
> +static void (*old_apm_get_power_status)(struct apm_power_info*);
> +
> +static int __init apm_battery_init(void)
> +{
> + printk(KERN_INFO "APM Battery Driver\n");
> +
> + old_apm_get_power_status = apm_get_power_status;
>
In article <[EMAIL PROTECTED]> you wrote:
>> Unfortunatelle Latency is critical for a number of critical applications
>> like databases or file based transaction systems (mail, news) - mainly the
>> users of fsync().
>
> Whether you mix audio in userspace or kernel does not impact latency -
> you
On 4/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Mon, Apr 16, 2007 at 03:03:16PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Mon, Apr 16, 2007 at 02:30:17PM -0400, Dmitry Torokhov wrote:
> >> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >> >Hi,
On Mon, 16 Apr 2007, Diego Calleja wrote:
El Mon, 16 Apr 2007 17:46:50 +0200 (CEST), Tomasz Kłoczko <[EMAIL PROTECTED]>
escribió:
also some other interestig numbers can be founnd on:
http://milek.blogspot.com/2006/08/hw-raid-vs-zfs-software-raid-part-ii.html
So software raid can be faster t
On 4/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Mon, Apr 16, 2007 at 03:47:13PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> >On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> >
> >> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >> > Hi,
> >> >
> >> >
On Fri, Apr 13, 2007 at 05:50:01PM +0400, Anton Vorontsov wrote:
> +/*
> + * include/linux/ioport.h does not provide flags for generic IRQ trigger
> + * types. So, we're using "ISA PnP IRQ specific bits", and converting them.
> + */
> +static unsigned int get_irq_flags(struct resource *res)
> +{
>
Update various mailing list addresses to use "lists.linux-foundation.org"
instead of "lists.osdl.org", to help phase out the old addresses.
Signed-off-by: David Brownell <[EMAIL PROTECTED]>
---
I *think* this generalizes beyond linux-pm ... and hey, maybe now I know why
the PM list spends so much
Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
>> I meant that the central requirement on the design and implementation of
>> audio subsystems is an (ideally guaranteed) bounded maximum of
>> latencies;
[...]
>> You were talking about throughput of storage systems, for which lat
On Mon, Apr 16, 2007 at 01:39:19PM -0600, Eric W. Biederman wrote:
> Miklos Szeredi <[EMAIL PROTECTED]> writes:
>
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > The owner doesn't need sysadmin capabilities to call umount().
> >
> > Similar behavior as umount(8) on mounts having "user=UID" op
On Mon, Apr 16, 2007 at 03:03:16PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >On Mon, Apr 16, 2007 at 02:30:17PM -0400, Dmitry Torokhov wrote:
> >> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >> >Hi,
> >> >
> >> >based on the discussion in "How shou
On Mon, Apr 16, 2007 at 03:47:13PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> >On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> >
> >> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >> > Hi,
> >> >
> >> > based on the discussion in "How should an exit r
On Mon, 16 Apr 2007, David Miller wrote:
> From: Andrew Vasquez <[EMAIL PROTECTED]>
> Date: Mon, 16 Apr 2007 09:37:12 -0700
>
> > On Mon, 16 Apr 2007, David Miller wrote:
> >
> > > But even if that fails, I think the fallback code should be put back,
> > > since it obviously was used by at least
From: David Miller <[EMAIL PROTECTED]>
Date: Mon, 16 Apr 2007 12:37:43 -0700 (PDT)
> Now I'm happy to code up the sparc OFW property bits but your attitude
> and perspective on this absolutely has to change and the old fallback
> code still has to go back in there, possible FC ID collisions or not
Jeff Chua wrote:
> On 4/16/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
>> Chipset limitation. It uses up most of the MMIO region above 3GB
>> preventing RAM from being mapped there, and doesn't support remapping
>> the covered RAM to above 4GB. Nothing the kernel can do about it.
>
> Well, I gue
> > > Hmm. pci_save_pcix_state/pci_restore_pcix_state seem to only handle
> > > regular devices and seem to ignore the fact that for bridge PCI-X
> > > capability has a different structure.
> > >
> > > Is this intentional?
> >
> > Probably not a such. I don't think we have any drivers for bridge
Quoting Eric W. Biederman ([EMAIL PROTECTED]):
> Miklos Szeredi <[EMAIL PROTECTED]> writes:
>
> >> > That depends. Current patches check the "unprivileged submounts
> >> > allowed under this mount" flag only on the requested mount and not on
> >> > the propagated mounts. Do you see a problem wit
On Mon, 16 Apr 2007, Greg KH wrote:
> On Mon, Apr 16, 2007 at 07:36:27PM +0200, Cornelia Huck wrote:
> > Grab and release the module kobject refcount if kobj->owner is set.
> > This prevents calls to the release function after the module has
> > been unloaded.
>
> But doesn't this cause reference
On Mon, 16 April 2007 17:46:50 +0200, Tomasz Kłoczko wrote:
> On Mon, 16 Apr 2007, Christoph Hellwig wrote:
>
> >Numbers, please. So far in all interesting benchmarks it actually
> >was slower. But when they're faster than XFS somewhere I'd defintly
> >be interesting in looking at why this is tr
On 4/16/07, Alan Stern <[EMAIL PROTECTED]> wrote:
On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > based on the discussion in "How should an exit routine wait for
> > release() callbacks?", I've cooked up some patches that make mo
Miklos Szeredi <[EMAIL PROTECTED]> writes:
> From: Miklos Szeredi <[EMAIL PROTECTED]>
>
> The owner doesn't need sysadmin capabilities to call umount().
>
> Similar behavior as umount(8) on mounts having "user=UID" option in
> /etc/mtab. The difference is that umount also checks /etc/fstab,
> pre
On Mon, Apr 16, 2007 at 12:14:27PM -0700, Matt Reimer wrote:
> On 4/15/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
> > > + di->update_time = jiffies;
> > > +
> > > + /* DS2760 reports voltage in units of 4.88mV, but the battery class
> > > + * reports in units of mV, so convert by mul
From: Andrew Vasquez <[EMAIL PROTECTED]>
Date: Mon, 16 Apr 2007 09:37:12 -0700
> On Mon, 16 Apr 2007, David Miller wrote:
>
> > But even if that fails, I think the fallback code should be put back,
> > since it obviously was used by at least one system and it's probable
> > that there are some ot
On Mon, 16 Apr 2007, Dmitry Torokhov wrote:
> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > based on the discussion in "How should an exit routine wait for
> > release() callbacks?", I've cooked up some patches that make module
> > unload wait until the last reference for a
On 4/16/07, Bernd Eckenfels <[EMAIL PROTECTED]> wrote:
In article <[EMAIL PROTECTED]> you wrote:
> I meant that the central requirement on the design and implementation of
> audio subsystems is an (ideally guaranteed) bounded maximum of
> latencies; and that's exactly the major point where I hear
On Mon, 16 Apr 2007, Hugh Dickins wrote:
> > > Compromise patch below: would that be satisfactory to you, David?
> >
> > I really like the patch, but for perhaps a slightly different reason:
> > we're only flushing ranges that have been shown to need it. We aren't
> > completely flushing the e
Quoting Miklos Szeredi ([EMAIL PROTECTED]):
> From: Miklos Szeredi <[EMAIL PROTECTED]>
>
> If MNT_USERMNT flag is not set in the target vfsmount, then
MNT_USER and MNT_USERMNT? I claim no way will people keep those
straight. How about MNT_ALLOWUSER and MNT_USER?
-serge
> unprivileged mounts w
In article <[EMAIL PROTECTED]> you wrote:
> I meant that the central requirement on the design and implementation of
> audio subsystems is an (ideally guaranteed) bounded maximum of
> latencies; and that's exactly the major point where I heard that there
> are problems with ALSA driver components i
Miklos Szeredi <[EMAIL PROTECTED]> writes:
>> > That depends. Current patches check the "unprivileged submounts
>> > allowed under this mount" flag only on the requested mount and not on
>> > the propagated mounts. Do you see a problem with this?
>>
>> I think privileges of this sort should pro
On 4/15/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
> + di->update_time = jiffies;
> +
> + /* DS2760 reports voltage in units of 4.88mV, but the battery class
> + * reports in units of mV, so convert by multiplying by 4.875.
> + * We approximate because integer math is cheap, an
On Mon, 16 Apr 2007, David Rientjes wrote:
>
> > Compromise patch below: would that be satisfactory to you, David?
>
> I really like the patch, but for perhaps a slightly different reason:
> we're only flushing ranges that have been shown to need it. We aren't
> completely flushing the entire
El Mon, 16 Apr 2007 17:46:50 +0200 (CEST), Tomasz Kłoczko <[EMAIL PROTECTED]>
escribió:
> also some other interestig numbers can be founnd on:
> http://milek.blogspot.com/2006/08/hw-raid-vs-zfs-software-raid-part-ii.html
So software raid can be faster than HW raid. News at 11.
-
To unsubscribe f
On 4/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Mon, Apr 16, 2007 at 02:30:17PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >based on the discussion in "How should an exit routine wait for
> >release() callbacks?", I've cooked up some patche
On Mon, Apr 16, 2007 at 07:36:19PM +0200, Cornelia Huck wrote:
> Hi,
>
> based on the discussion in "How should an exit routine wait for
> release() callbacks?"
Wait, why is this needed anymore with the recent work in splitting sysfs
away from the backing code?
thanks,
greg k-h
-
To unsubscribe
On Mon, 16 Apr 2007, Hugh Dickins wrote:
> When, as now, core mm people make some change, failing to take your
> case into account.
>
That's exactly what happened here: include/asm-i386/pgtable.h is
advertising both __HAVE_ARCH_PTEP_TEST_AND_CLEAR_{DIRTY,YOUNG} without
actually having them. N
On Mon, Apr 16, 2007 at 02:30:17PM -0400, Dmitry Torokhov wrote:
> On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
> >Hi,
> >
> >based on the discussion in "How should an exit routine wait for
> >release() callbacks?", I've cooked up some patches that make module
> >unload wait until the last
Hi Jakub,
> That would mean an additional syscall. Furthermore, if you allocate a big
> chunk of memory, dirty it, then free (with madvise (MADV_FREE)) it and soon
> allocate the same size of memory again, it is better to start that with
> non-dirty memory, it might be that this time you e.g. d
On 10:46 Mon 16 Apr , Roland Dreier wrote:
> > - down_interruptible(&info->write_sem);
> > + if(mutex_lock_interruptible(&info->write_lock)){
> > + return -ERESTARTSYS;
> > + }
>
> 1) This is a semantic change. Of course using down_interruptible()
> without checking the return
On 4/16/07, Cornelia Huck <[EMAIL PROTECTED]> wrote:
Hi,
based on the discussion in "How should an exit routine wait for
release() callbacks?", I've cooked up some patches that make module
unload wait until the last reference for a kobject has been dropped.
This should plug the "release function
Pavel Machek wrote:
> David Wagner wrote:
>> There was no way to follow fork securely.
>
>Actually there is now. I did something similar called subterfugue and
>we solved this one.
Yes, I saw that. I thought subterfugue was neat. The way that
subterfugue was a clever hack -- albeit too clever b
On Sat, 2007-04-14 at 17:20 -0700, Michael Chan wrote:
> I also like Andi's idea of using change_page_attr() to isolate the
> problem. I'll try to send you a debug patch in the next few days to try
> that out. Thanks.
>
Here's the debug patch for x86 only that will change the statistics
memory
Jeff Chua wrote:
> On 4/16/07, Stefan Richter <[EMAIL PROTECTED]> wrote:
>> The X60 most certainly contains a chipset which severely limits the
>> amount of accessible RAM due to issues with remapping of PCIe addresses.
...
> I wondered if there's anyone working on a patch for this.
All I heard of
Mikko Tiihonen <[EMAIL PROTECTED]> writes:
> It looks probable that most NVidia chipsets have the HPET address at
> 0x44. It might be possible to enable the HPET even if BIOS did not
That seems like a dangerous assumption. If anything this needs to be keyed
on specific PCI IDs.
And the way you
Tomasz Kłoczko wrote:
> On Mon, 16 Apr 2007, Stefan Richter wrote:
>> Tomasz Kłoczko wrote:
>>> Current FUSE implemntation can't be
>>> comparable in aspects of speed and probably never will be on using
>>> threads
>>
>> Did you measure this on a few hardwares and workloads?
>
> Before asking firs
[cc:ed to netdev]
On Sun, Apr 15, 2007 at 10:45:37PM -0700, Mike Mattie wrote:
> Hello,
>
> netconsole is hanging my box during IDE init.
>
> I am running 2.6.20.7, config is attached from /proc
>
> Without using netconsole the kernel boots fine. I am writing this message
> from it.
>
> When
On Mon, Apr 16, 2007 at 07:36:27PM +0200, Cornelia Huck wrote:
> Grab and release the module kobject refcount if kobj->owner is set.
> This prevents calls to the release function after the module has
> been unloaded.
But doesn't this cause reference counts to be grabbed on modules that
don't want
On Fri, 13 Apr 2007, Zachary Amsden wrote:
>
> If the logic is too difficult to reason about without entering ganda
> bherundasana, then it is simpler to just drop the _defer suffix. Old / young
> actually is just as serious, not because A-bit is critical (although
> misvirtualizing it will do st
> > > > > Also for bind-mount and remount operations the flag has to be
> > > > > propagated
> > > > > down its propagation tree. Otherwise a unpriviledged mount in a
> > > > > shared
> > > > > mount wont get reflected in its peers and slaves, leading to
> > > > > unidentical
> > > > > shared-s
As the new mutex primitive is now in place, I read,it is advised
not to use binary semaphore for mutual exclusion.
while looking at different place where a binary semaphore is initialized,
I came accross bd_mount_sem.
I read a thread on LKML few months back related to the bd_mount_sem
This showed up during a 2.6.21-rc7 build after I upgraded gcc from 3.3
to 3.4 on a Slackware system:
make -C drivers/scsi/aic7xxx/aicasm
(...)
gcc -I/usr/include -I. aicasm.c aicasm_symbol.c aicasm_gram.c
aicasm_macro_gram.c aicasm_scan.c aicasm_macro_scan.c -o aicasm -ldb
aicasm_gram.y:1948: err
> -down_interruptible(&info->write_sem);
> +if(mutex_lock_interruptible(&info->write_lock)){
> +return -ERESTARTSYS;
> +}
1) This is a semantic change. Of course using down_interruptible()
without checking the return value is almost certainly a bug, but have
you though
On Mon, 2007-04-16 at 11:56 +0200, Miklos Szeredi wrote:
> > > > Also for bind-mount and remount operations the flag has to be propagated
> > > > down its propagation tree. Otherwise a unpriviledged mount in a shared
> > > > mount wont get reflected in its peers and slaves, leading to unidentical
Use mutex instead of binary semaphore for mutual exclusion.
Signed-off-by: Milind Arun Choudhary <[EMAIL PROTECTED]>
---
rocket.c | 22 --
rocket_int.h |2 +-
2 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/drivers/char/rocket.c b/drivers/char/rock
Hi,
based on the discussion in "How should an exit routine wait for
release() callbacks?", I've cooked up some patches that make module
unload wait until the last reference for a kobject has been dropped.
This should plug the "release function in already deleted module" race;
however, if the last
Make module->mkobj.kobj useful for refcounting, even if sysfs is
not used.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
---
include/linux/module.h | 14 +-
kernel/module.c|2 --
kernel/params.c| 14 +-
3 files changed, 6 insertions(+), 24 delet
Expose module->mkobj.kobj refcounting to drivers. Wait with deleting
the module until the refcount has dropped to 0.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
---
include/linux/module.h |4
kernel/module.c| 30 +-
kernel/params.c|
Grab and release the module kobject refcount if kobj->owner is set.
This prevents calls to the release function after the module has
been unloaded.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
---
include/linux/kobject.h |1 +
lib/kobject.c |6 +-
2 files changed, 6 ins
Peter Williams wrote:
To my mind scheduling
and load balancing are orthogonal and keeping them that way simplifies
things.
Scuse me if I jump in here, but doesn't the load balancer need some way
to figure out a) when to run, and b) which tasks to pull and where to
push them?
I suppose you
On Mon, Apr 16, 2007 at 05:27:51PM +0200, Tomasz Kłoczko wrote:
> On Mon, 16 Apr 2007, Adrian Bunk wrote:
>
>> On Mon, Apr 16, 2007 at 04:01:23PM +0200, Tomasz Kłoczko wrote:
>>> ...
>>> Few days ago I'm swich two backup servers with few TB storage from Linux
>>> to
>>> Solaris .. only because cli
[resend, chaning linux-ide to lkml]
On Thu, 5 Apr 2007 14:20:01 -0700 Andrew Morton wrote:
> hm. Well, what to do?
>
> How about we prevail upon Randy to:
>
> - rename pci_set_mwi() to pci_try_set_mwi()
>
> - make it return 0 on success, 1 if the "try" failed
>
> - make it return -EFOO on err
Andreas Gruenbacher wrote:
On Monday 16 April 2007 18:42, Randy Dunlap wrote:
Please don't use the kernel-doc begin-marker "/**" when the comment block
isn't in kernel-doc format.
Sigh, kernel-doc should improve things, not get in the way ...
Well, I see it as sort of a language that is embe
On Mon, Apr 16, 2007 at 06:40:41PM +0200, Andreas Gruenbacher wrote:
> On Monday 16 April 2007 18:21, Christoph Hellwig wrote:
> > But anyway, creating fake nameidata structures is not really helpful.
> > If there is a nameidata passed people expect it to be complete, and
> > if you pass them to an
On Monday 16 April 2007 18:42, Randy Dunlap wrote:
> Please don't use the kernel-doc begin-marker "/**" when the comment block
> isn't in kernel-doc format.
Sigh, kernel-doc should improve things, not get in the way ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On Mon, 16 Apr 2007 18:29:20 +0200 Andreas Gruenbacher wrote:
> Here is a patch with request for comment.
>
> --- a/include/linux/namei.h
> +++ b/include/linux/namei.h
> @@ -14,21 +14,39 @@ struct open_intent {
>
> enum { MAX_NESTED_LINKS = 8 };
>
> +/**
Please don't use the kernel-doc begi
101 - 200 of 354 matches
Mail list logo
