thanks, applied.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Thanks, applied.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Mar 22, 2007 at 06:43:21PM +0100, Mattia Dongili wrote:
> On Thu, Mar 22, 2007 at 06:02:01PM +0100, Mattia Dongili wrote:
>
> forgot... (should I resend the whole thing?)
>
> Signed-off-by: Mattia Dongili <[EMAIL PROTECTED]>
Nah, I'll cut-n-paste.
Ignore my other mail btw, I wasn't
On Thu, 22 Mar 2007 12:06:40 -0400 Jeff Dike <[EMAIL PROTECTED]> wrote:
> These are post-2.6.21 material, except that if the new definition of
> ARRAY_SIZE goes to Linus, patch 1 in this series should go as well.
I have the ARRAY_SIZE change queued for 2.6.22.
It looks like the UML change needs
On Thu, 22 Mar 2007 10:36:16 +0200 Tasos Parisinos wrote:
> > Hi,
> > Lots of good progress here, but still a few comments below.
> >
> > Needs to apply to current mainline.
> >
> >
> What do you mean by mainline?
Linus's current kernel tree, i.e., the latest git tree or
git snapshot
On Thu, Mar 22, 2007 at 06:02:01PM +0100, Mattia Dongili wrote:
forgot... (should I resend the whole thing?)
Signed-off-by: Mattia Dongili <[EMAIL PROTECTED]>
--
mattia
:wq!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
If I set /proc/sys/vm/dirty_ratio to "5" the write lockup happens within
the first MilliSecond, at about 100MB per file system.
If I slew the dirty_ratio to 80, the lockup happens
at about 2GB per file system.
2.6.21-rc4 has the same symptoms, and same lockups.
It appears that mptsas is dropping
Hi,
On Wed, Mar 21, 2007 at 08:04:00PM +0100, Johannes Weiner wrote:
> Did I even get the right place on where the NULL pointer dereference
> happens? :)
No, I did not. Sorry for the noise.
=Hannes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Thu, 22 Mar 2007 14:25:42 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> Additions and removal from tty_drivers list were just done as well as
> iterating on it for /proc/tty/drivers generation.
>
> testing: modprobe/rmmod loop of simple module which does nothing but
>
On Thursday 22 March 2007 17:00, Joachim Fenkes wrote:
> Example:
>
> Add a device "/proc/device-tree/[EMAIL PROTECTED]" to ibmebus like this:
> echo /[EMAIL PROTECTED] > /sys/bus/ibmebus/probe
>
> Remove the device like this:
> echo /[EMAIL PROTECTED] > /sys/bus/ibmebus/remove
>
Of
Hi,
On Thu, Mar 22, 2007 at 05:26:04PM +0100, Johannes Weiner wrote:
> > The code in there is irksome - it'd be nice to find some way of
> > restructuring it to make it less obscure, and to kill that warning.
>
> Functionscope or filescope? ;)
Oh well... I think the latter. I wil clean it up
In sd_revalidate_disk(), the SCSI Disk driver needs a few bytes DMA memory,
allocated by kmalloc() and __GFP_DMA. This patch uses __GFP_DMA only if
the corresponding host structure has unchecked_isa_dma set.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
drivers/scsi/sd.c |3 ++-
1
Con Kolivas wrote:
> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote:
>> Andy Whitcroft wrote:
>>> Andy Whitcroft wrote:
Andrew Morton wrote:
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>
> Will appear later at
>
>
>
On Thu, 22 Mar 2007 07:23:06 -0500,
Larry Finger <[EMAIL PROTECTED]> wrote:
> Cornelia Huck wrote:
> > On Wed, 21 Mar 2007 23:39:17 -0800,
> > Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> >> On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <[EMAIL PROTECTED]> wrote:
> >>
> >>> With the latest
On Wed, Mar 21, 2007 at 08:10:42PM -0800, Andrew Morton wrote:
> On Wed, 21 Mar 2007 21:00:06 -0700 Greg KH <[EMAIL PROTECTED]> wrote:
>
> > On Wed, Mar 21, 2007 at 11:51:04PM -0400, Dave Jones wrote:
> > > On Wed, Mar 21, 2007 at 08:07:53PM -0700, Greg KH wrote:
> > >
> > > > > After
This patch includes:
- code cleanup related to resource management
- extended error data gathering for resource management
- removing trailing whitespaces
Signed-off-by: Jan-Bernd Themann <[EMAIL PROTECTED]>
---
This patch applies on top of the netdev upstream branch for 2.6.22
The patch fixes bugs related to the probe / remove adapter
functionality (handling of OFDT nodes)
Signed-off-by: Jan-Bernd Themann <[EMAIL PROTECTED]>
---
This patch applies on top of the netdev upstream branch for 2.6.22
diff --git a/drivers/net/ehea/ehea.h b/drivers/net/ehea/ehea.h
index
> Sounds like you have a fundamentally incompatible set of requirements.
Sounds so yep :)
> Why do you need the softlockup watchdog if you intend to induce soft
> lockups on purpose?
It's a condition of a customer of us, so I can't change it.
But it happens not often that my part is used. So I
On Wed, 2007-03-21 at 16:57 -0700, Greg KH wrote:
> On Wed, Mar 21, 2007 at 09:37:52AM -0400, Daniel Yeisley wrote:
> > On Tue, 2007-03-20 at 13:26 -0700, Greg KH wrote:
> > > On Tue, Mar 20, 2007 at 01:25:38PM -0400, Daniel Yeisley wrote:
> > > > On Tue, 2007-03-20 at 11:00 -0700, Greg KH wrote:
On Thu, Mar 22, 2007 at 04:25:53PM +, David Woodhouse wrote:
> On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote:
> > Yep - realized this when I took a closer look.
> > One thing striked my mind. It is correct that new things gets added
> > to i386 first these days?
>
> Personally I tend
On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote:
> Yep - realized this when I took a closer look.
> One thing striked my mind. It is correct that new things gets added
> to i386 first these days?
Personally I tend to do PowerPC first, but most others seem to do i386,
yes. There are still
Hi,
On Thu, Mar 22, 2007 at 12:45:40AM -0800, Andrew Morton wrote:
> > On Thu, Mar 22, 2007 at 12:48:05AM +0100, roland wrote:
> > > fs/block_dev.c: In function `bd_claim_by_kobject':
> > > fs/block_dev.c:953: warning: `found' might be used uninitialized in this
> > > function
> >
> > found
I cannot reproduce the BUG with your ml.bz2 patch applied.
I am seeing this with both 2.6.21-rc4-mm1 + hotfixes, and with
2.6.21-rc4 + ml.bz2:
Mar 22 09:10:35 FractalPath kernel: ACPI: CPU0 (power states: C1[C1]
C2[C2] C3[C3])
Mar 22 09:10:35 FractalPath kernel: The kobject at, or inside
On 3/22/07, Cestonaro, Thilo (external)
<[EMAIL PROTECTED]> wrote:
> Just disable the softlockup watchdog.
Thx for your answer, but this is no option for me, as I said in my first post
:(.
Sounds like you have a fundamentally incompatible set of requirements.
Why do you need the softlockup
William Lee Irwin III wrote:
> Any chance we can get some kind of devices set up for partitions of
> loop devices if we're going to redo loopdev setup? That's been a thorn
> in my side for some time.
This script might be of use:
http://www.pixelbeat.org/scripts/lomount.sh
cheers,
Pádraig.
-
To
The build started finding calls from non-init to init functions.
These are just cases of init functions not being properly marked, so
this patch fixes that.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/kernel/mem.c|2 +-
arch/um/os-Linux/main.c |2 +-
This patch narrows the sigio interface. The boot-time SIGIO testing
used to be in start_up.c, which meant that pty_output_sigio and
pty_close_sigio needed to be global. By moving that code here, those
can become static and the declarations moved from user_util.h.
os_check_bugs is also here
user_util.h isn't needed any more, so delete it and remove all
includes of it.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/drivers/chan_kern.c |1
arch/um/drivers/chan_user.c |1
arch/um/drivers/cow_sys.h|1
Rescue the useful contents of the soon-to-be-gone user-util.h.
pty.c now gets ptsname from stdlib.h like it should have always done.
CATCH_EINTR is now in os.h, although perhaps all usage should be under
os-Linux at some point.
get_pty is also in os.h.
This patch restores the old definition of
This is the minimal change needed to keep UML building with the new
definition of ARRAY_SIZE. It is defined in user_util.h so that
userspace files, which can't include kernel.h, can still use
ARRAY_SIZE. However, since user_util.h is included everywhere,
including kernel files, the token
This patch moves the declarations of the architecture hooks from
user_util.h to a new header, arch.c, and adds the necessary includes
to files which need those declarations.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/include/arch.h | 15 +++
This patch moves all the the symbols defined in um_arch.c, which are
mostly boundaries between different parts of the UML kernel address
space, to a new header, as-layout.h. There are also a few things here
which aren't really related to address space layout, but which don't
really have a better
These are post-2.6.21 material, except that if the new definition of
ARRAY_SIZE goes to Linus, patch 1 in this series should go as well.
These patches are a response to the new ARRAY_SIZE. UML had a
duplicate definition for the use of the userspace side of things,
which can't directly use
I wrote:
More details on what the patch does:
* Rewords the description of CONFIG_NLS_DEFAULT, because at some point
in the past it confused some people
* Removes CONFIG_FAT_DEFAULT_IOCHARSET, now CONFIG_NLS_DEFAULT is used
for this purpose. This is because the correct setting of both must
In some cases, multiple OFDT nodes might share the same location code, so
the location code is not a unique identifier for an OFDT node. Changed the
ibmebus probe/remove interface to use the DT path of the device node instead
of the location code.
The DT path must be written into probe/remove
Rusty,
On Thu, 22 Mar 2007 20:24:10 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-03-22 at 09:10 +0100, Sébastien Dugué wrote:
> > Why not take on the opportunity to rename boot_gt_table to boot_gtd,
> > to avoid the duplicate T(able)?
>
> That's not a bad idea, but IMHO
On Wed, Mar 21, 2007 at 06:15:47PM +0200, Marti Raudsepp wrote:
> >On Tue, Mar 20, 2007 at 12:34:08PM +0200, Marti Raudsepp wrote:
> >lvmove
> >> wouldn't move the partition back to /dev/sda5 after "defragmenting" it.)
> However, when attempting to move back the LV, the allocater can create two
eHCA scaling code must not depend on register_cpu_notifier() if
CONFIG_HOTPLUG_CPU is not set, so put all related code into #ifdefs.
Signed-off-by: Joachim Fenkes <[EMAIL PROTECTED]>
---
ehca_irq.c |8
1 file changed, 8 insertions(+)
diff --git
On Wednesday 21 March 2007 18:03, johann deneux wrote:
> On 3/21/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
> > Dmitry Torokhov napsal(a):
> > > On 3/21/07, johann deneux <[EMAIL PROTECTED]> wrote:
> > >> I would suggest adding a new effect type (3d effect) and extending the
> > >> union in struct
Hi,
On Thu, 22 Mar 2007, Alexander E. Patrakov wrote:
> > hfs has a codepage option as well, but I don't know its default in the
> > various countries, but it could be different from DOS.
>
> Yes. Since this comes from Mac world, it definitely makes sense to add
> CONFIG_MAC_CODEPAGE_DEFAULT,
> Just disable the softlockup watchdog.
Thx for your answer, but this is no option for me, as I said in my first post
:(.
Thilo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On (22/03/07 10:38), Christoph Hellwig didst pronounce:
> On Wed, Mar 21, 2007 at 02:43:48PM -0500, Adam Litke wrote:
> > The main reason I am advocating a set of pagetable_operations is to
> > enable the development of a new hugetlb interface. During the hugetlb
> > BOFS at OLS last year, we
Handle build_phys_page_list() failure in iwch_reregister_phys_mem().
Signed-off-by: Steve Wise <[EMAIL PROTECTED]>
---
drivers/infiniband/hw/cxgb3/iwch_provider.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/infiniband/hw/cxgb3/iwch_provider.c
Hi Nicolas,
On Monday 19 March 2007 01:19, Nicolas Boichat wrote:
> + /* initialize the input class */
> + applesmc_idev->name = "applesmc";
You may want to set applesmc_idev->id.bus = BUS_HOST;
> + applesmc_idev->cdev.dev = >dev;
> + applesmc_idev->evbit[0] =
On Thu, 2007-03-22 at 08:28 -0700, Greg KH wrote:
> On Tue, Mar 20, 2007 at 11:54:03AM +, Pavel Machek wrote:
> > Hi!
> >
> > > [EMAIL PROTECTED]:/home/maxim# cat
> > > /sys/devices/system/clockevents/clockevents0/registered
> > > lapicF:0007 M:3(periodic) C: 1
> > > hpet
On Tue, Mar 20, 2007 at 11:54:03AM +, Pavel Machek wrote:
> Hi!
>
> > [EMAIL PROTECTED]:/home/maxim# cat
> > /sys/devices/system/clockevents/clockevents0/registered
> > lapicF:0007 M:3(periodic) C: 1
> > hpet F:0003 M:1(shutdown) C: 0
> > lapic
Ian Kent <[EMAIL PROTECTED]> writes:
> btw please don't be confused by my use of "user space application". In
> my comments I'm talking about applications that are similar in function
> to autofs itself and not processes that might trigger mounts. For
> example the "autodir" package uses the
Really, I dont think Tomas has the skill or time to follow a typical
lkml discussion.
Well I have the skills to follow LKML discussion, but I don't have the
skills to provide *perfect* patch for loop.c
So I'm offering a financial reward for the *perfect* loop.c patch.
It should support *A
On 3/22/07, Cestonaro, Thilo (external)
<[EMAIL PROTECTED]> wrote:
> You didn't explain _why_ you need to sleep for such a long time,
> and as you didn't give a pointer to your code, there's not
> much people can do to recommend changes other than "don't do that".
The code which is executed
Ian Kent <[EMAIL PROTECTED]> writes:
> On Wed, 2007-03-21 at 15:58 -0500, Serge E. Hallyn wrote:
>> PS
>> Note that if I'm right, but some machine starts autofs in a child
>> pid_namespace, the pid_nr() the way I have it is wrong. I'm not sure in
>> that case how we go about fixing that.
On Thu, 22 Mar 2007, Nick Piggin wrote:
>
> Nothing sleeps on PageUptodate, so I don't think that could explain it.
Good point. I forget that we just test "uptodate", but then always sleep
on "locked".
> The fs: fix __block_write_full_page error case buffer submission patch
> does change the
On Thu, 2007-03-22 at 07:11 -0700, William Lee Irwin III wrote:
> On Thu, Mar 22 2007, Eric Dumazet wrote:
> >> Sure, but it's the first Tomas patch :)
>
> On Thu, Mar 22, 2007 at 02:54:57PM +0100, Jens Axboe wrote:
> > The more the reason to guide him in the direction of a right solution,
> >
I'd like to mention what might be a new twist on this problem. We are
seeing the same kind of 4k-block data corruption on multiple Tyan
dual-Opteron boards (S3870) with a ServerWorks chipset, not Nvidia. I
wonder if it really an Nvidia-specific issue. The Nvidia boards are a
lot more popular,
On Thu, 2007-03-22 at 15:16 +0100, Adrian Bunk wrote:
> > > Does it work if you do _not_ revert the commits, and instead replace in
> > > drivers/acpi/processor_idle.c the
> > > #ifdef ARCH_APICTIMER_STOPS_ON_C3
> > > with an
> > > #if 0
> > > ?
> >
> > Then NOAPIC probably works again, but
Hi!
> > suspend (to RAM and disk) broke on my Thinkpad R60 (Core 2 Duo laptop)
> > somewhere between 2.6.20 and 2.6.21-rc3
>
> I just tried -rc4, and it's still broken.
Try disabling hires timers and no_hz.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
Hi!
> [EMAIL PROTECTED]:/home/maxim# cat
> /sys/devices/system/clockevents/clockevents0/registered
> lapicF:0007 M:3(periodic) C: 1
> hpet F:0003 M:1(shutdown) C: 0
> lapicF:0007 M:3(periodic) C: 0
> [EMAIL PROTECTED]:/home/maxim#
Now... this
On Thu, 2007-03-22 at 08:31 -0500, Serge E. Hallyn wrote:
> > >
> > > From: "Serge E. Hallyn" <[EMAIL PROTECTED]>
> > > Subject: [PATCH] autofs: prevent pid wraparound in waitqs
> > >
> > > Instead of storing pid numbers for waitqs, store references
> > > to struct pids. Also store a reference
On Thu, 2007-03-22 at 15:33 +0100, Herbert Poetzl wrote:
> On Thu, Mar 22, 2007 at 11:28:43AM +0900, Ian Kent wrote:
> > On Wed, 2007-03-21 at 15:58 -0500, Serge E. Hallyn wrote:
> > > Quoting Eric W. Biederman ([EMAIL PROTECTED]):
> > > > "Serge E. Hallyn" <[EMAIL PROTECTED]> writes:
> > > >
> >
Michael Ellerman <[EMAIL PROTECTED]> writes:
> This is my series to rework the generic MSI code into something we can use
> on powerpc[1].
>
> I've tried as much as possible not to change the semantics for other archs,
> but there's a few little changes. I think they're all OK in their own right.
Roman Zippel wrote:
hfs has a codepage option as well
Is it _currently_ useful at all? The problem is that the kernel has no nls
modules for Mac codepages (e.g., MacRoman which is cp1).
--
Alexander E. Patrakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Thu, 2007-03-22 at 08:31 -0500, Serge E. Hallyn wrote:
> Quoting Ian Kent ([EMAIL PROTECTED]):
> > On Wed, 2007-03-21 at 21:19 -0500, Serge E. Hallyn wrote:
> > > Quoting Ian Kent ([EMAIL PROTECTED]):
> > > > On Tue, 2007-03-20 at 16:01 -0600, Eric W. Biederman wrote:
> > > > > "Serge E.
On Thu, Mar 22, 2007 at 09:39:09AM -0500, Serge E. Hallyn wrote:
> > What troubles will mounting both cpuset and ns in the same hierarchy
> > cause?
>
> Wow, don't recall the full context here.
Sorry to have come back so late on this :)
> But at least with Paul's container patchset, a subsystem
Hello List!
I'm using the new scheduler since a few days and I have to say that this is an
amazing improvement for gaming loads. When playing enemy-territory the
animations are completly smooth and fluid, without any hiccups. Et runs now
clearly better on Linux than on my Win XP partition
Quoting Srivatsa Vaddagiri ([EMAIL PROTECTED]):
> On Fri, Mar 09, 2007 at 10:50:17AM -0600, Serge E. Hallyn wrote:
> > The nsproxy container subsystem could be said to be that unification.
> > If we really wanted to I suppose we could now always mount the nsproxy
> > subsystem, get rid of
Nick Piggin wrote:
> Forward port of nicksched to 2.6.21-rc4.
Great!
> Can't find my old
> design/description document for it, but it is yet another scheduler. Focus
> is on simplicity and fairness.
Simplicity is really key.
> This one tends to require X to be reniced to -10 or so for best
Robert Hancock thought this was a hardware problem.
He was right.
I switched around cables on the hot-swap backplane, figuring that I
would determine whether I had a bad cable or a bad backplane ( hoping
for a bad cable ) and the problem went away. One of the cables wasn't
seated properly
On Thu, Mar 22, 2007 at 11:28:43AM +0900, Ian Kent wrote:
> On Wed, 2007-03-21 at 15:58 -0500, Serge E. Hallyn wrote:
> > Quoting Eric W. Biederman ([EMAIL PROTECTED]):
> > > "Serge E. Hallyn" <[EMAIL PROTECTED]> writes:
> > >
> > > >> > void autofs4_dentry_release(struct dentry *);
> > > >> >
On Thu, Mar 22, 2007 at 02:42:31PM +0100, Jens Axboe wrote:
> But this still wastes memory, why not just allocate each loop device
> dynamically when it is set up? The current approach is crap, it is just
> wasting memory for loop devices, queues, etc.
Correction: current ABI is crap. To set the
You might want a more radical patch :
I agree that my patch is not the perfect solution for max_loop problem.
But it nearly doubles max_loop for me (using 386 arch) and moreover it
is a FIX for incorrect implementation in kernel IMHO. So I can see
REASON to include it in Kernel. Do I cry at
Michael Ellerman <[EMAIL PROTECTED]> writes:
> Currently we never clear the msi_desc pointer in the irq_desc. This
> leaves us with a pointer to free'ed memory hanging around. No one seems
> to have hit this, so presumably other parts of the code are protecting
> us from ever using the stale
On Thu, Mar 22, 2007 at 03:10:03PM +0100, Thomas Gleixner wrote:
> On Thu, 2007-03-22 at 14:42 +0100, Adrian Bunk wrote:
> > > Starting with head as of yesterday and reverting two commits (that are
> > > duplicates of each other -- the same commit came into Linus's tree via
> > > two different
On Thu, Mar 22 2007, Eric Dumazet wrote:
>> Sure, but it's the first Tomas patch :)
On Thu, Mar 22, 2007 at 02:54:57PM +0100, Jens Axboe wrote:
> The more the reason to guide him in the direction of a right solution,
> instead of extending the current bad one!
On Thu, Mar 22 2007, Eric Dumazet
On Thu, 2007-03-22 at 14:42 +0100, Adrian Bunk wrote:
> > Starting with head as of yesterday and reverting two commits (that are
> > duplicates of each other -- the same commit came into Linus's tree via
> > two different paths) 'fixes' the problem for me. I'll let those with the
> > big brains
On Fri, Mar 09, 2007 at 10:50:17AM -0600, Serge E. Hallyn wrote:
> The nsproxy container subsystem could be said to be that unification.
> If we really wanted to I suppose we could now always mount the nsproxy
> subsystem, get rid of tsk->nsproxy, and always get thta through it's
> nsproxy
On Thu, Mar 22 2007, Eric Dumazet wrote:
> On Thu, 22 Mar 2007 14:42:31 +0100
> Jens Axboe <[EMAIL PROTECTED]> wrote:
>
>
> > > This time, you would be limited to 16384 loop devices on x86_64, 32768 on
> > > i386 :)
> >
> > But this still wastes memory, why not just allocate each loop device
>
Roman Zippel wrote:
hfs has a codepage option as well, but I don't know its default in the
various countries, but it could be different from DOS.
Yes. Since this comes from Mac world, it definitely makes sense to add
CONFIG_MAC_CODEPAGE_DEFAULT, the corresponding module parameter, and make
oh - i forgot sending this to the list, since this was copy via
webmailer.
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> Gesendet: 22.03.07 14:42:45
> An: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED]
> Betreff: Re: max_loop limit
> Hi Tomas,
>
> you`re completely right.
>
On Thu, 22 Mar 2007 14:42:31 +0100
Jens Axboe <[EMAIL PROTECTED]> wrote:
> > This time, you would be limited to 16384 loop devices on x86_64, 32768 on
> > i386 :)
>
> But this still wastes memory, why not just allocate each loop device
> dynamically when it is set up? The current approach is
Hi,
On Thu, 22 Mar 2007, Alexander E. Patrakov wrote:
> It is exposed as a mount parameter and kernel configuration option only for
> fat and smbfs (the two filesystems that my patch touches for this matter), and
> both of these filesystems come from DOS days, where there was one codepage for
>
On Thu, Mar 22 2007, Eric Dumazet wrote:
> On Thu, 22 Mar 2007 12:37:54 +0100
> Tomas M <[EMAIL PROTECTED]> wrote:
>
> > The question is not "Why do we need more than 255 loops?".
> > The question should be "Why do we need the hardcoded 255-limit in kernel
> > while there is no reason for it at
On Wed, Mar 21, 2007 at 09:03:06AM -0700, Ray Lee wrote:
> Hey Thomas, Ingo, et al.
>
> I'm having a problem, and tracked it down to what looks like a harmless
> commit of yours. I didn't quite believe the bisect at first, so tested
> it multiple times.
>
> The original problem report, when I
On Thu, 22 Mar 2007 12:37:54 +0100
Tomas M <[EMAIL PROTECTED]> wrote:
> The question is not "Why do we need more than 255 loops?".
> The question should be "Why do we need the hardcoded 255-limit in kernel
> while there is no reason for it at all?"
>
> My patch simply removes the hardcoded
Con Kolivas wrote:
> Here is the best fix for the bug pointed out. Thanks.
> Ensure niced tasks are not inappropriately limiting sleeping unniced tasks
> by explicitly checking what the best static priority that has run this
> major rotation was.
yes, this made the machine usable again.
After
Quoting Ian Kent ([EMAIL PROTECTED]):
> On Wed, 2007-03-21 at 21:19 -0500, Serge E. Hallyn wrote:
> > Quoting Ian Kent ([EMAIL PROTECTED]):
> > > On Tue, 2007-03-20 at 16:01 -0600, Eric W. Biederman wrote:
> > > > "Serge E. Hallyn" <[EMAIL PROTECTED]> writes:
> > > >
> > > > >> > void
Quoting Eric W. Biederman ([EMAIL PROTECTED]):
> "Serge E. Hallyn" <[EMAIL PROTECTED]> writes:
> >
> > So is the pid used for anything other than debugging?
> >
> > In any case, here is a replacement patch which sends the pid number
> > in the pid_namespace of the process which did the autofs4
Michal Piotrowski napisał(a):
> On 22/03/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
>>
>> * Michal Piotrowski <[EMAIL PROTECTED]> wrote:
>>
>> > Hi Ingo,
>>
>> > 2.6.21-rc4-rt0
>>
>> > BUG: at kernel/fork.c:1033 copy_process()
>>
>> thanks Michal - this is a real bug that affects upstream too.
I couldn't find the original thread so I am restarting one adding I hope
the appropriate people to the cc list.
Andrew thanks for forwarding this one. I finally see enough of this to
see what is going on.
The question is about the following sequence from libata.
pci_enable_msi();
Roman Zippel wrote:
I agree that these parameters should be changable not just at compile time
and the iocharset should be a global default, but the on disk encoding is
often filesystem specific, so I'd rather keep this option per filesystem.
You are right, the on-disk encoding is filesystem
(Please don't trim me from the CC list if you're replying to what I've said,
thanks.)
On Thu, March 22, 2007 00:31, David Schwartz wrote:
>> If you can't read protect your kernel, you can't write protect it
>> either.
>
> This is so misleading as to basically be false.
Please elaborate. Short of
On Thu, 2007-03-22 at 12:56 +0300, Alexey Dobriyan wrote:
> Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
> ---
>
> fs/proc/inode.c |5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> --- a/fs/proc/inode.c
> +++ b/fs/proc/inode.c
> @@ -167,8 +167,9 @@ static loff_t
Hi,
On Sun, 18 Mar 2007, Alexander E. Patrakov wrote:
> More details on what the patch does:
>
> * Rewords the description of CONFIG_NLS_DEFAULT, because at some point in the
> past it confused some people
> * Removes CONFIG_FAT_DEFAULT_IOCHARSET, now CONFIG_NLS_DEFAULT is used for
> this
On 22/03/07, Ingo Molnar <[EMAIL PROTECTED]> wrote:
* Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Hi Ingo,
> 2.6.21-rc4-rt0
> BUG: at kernel/fork.c:1033 copy_process()
thanks Michal - this is a real bug that affects upstream too. Find the
fix below - i've test-booted it and it fixes the
On Wed, 2007-03-21 at 20:59 +0100, Jens Axboe wrote:
> On Wed, Mar 21 2007, Dale Blount wrote:
> > On Wed, 2007-03-21 at 14:09 -0400, Chuck Ebbert wrote:
> > > Dale Blount wrote:
> > > >> I'm puzzled why this is hitting Dan, but no one else has reported
> > > >> anything. Dan, did 2.6.19 work for
Hi folks.
1) Are there any new developments in this issue? Does someone know if
AMD and Nvidia is still investigating?
2) Steve Langasek from Debian sent me a patch that disables the hw-iommu
per default on Nvidia boards.
I've attached it in the kernel bugzilla and asked for inclusion in the
This is a uniprocessor AMD64 system running software RAID-5 and RAID-10
over multiple PCIe SiI3132 SATA controllers. The hardware has been very
stable for a long time, but has been acting up of late since I upgraded
to 2.6.20.3. ECC memory should preclude the possibility of bit-flip
errors.
I use 2.6.20.2 kernel with ext3 rootfs on 4Gb SD on sharp zaurus sl-750
(PXA255).
After suspend/resume filesystem stay clean. But some i-nodes become broken.
Some files looks like block device or pipe with strange permissions, owner etc.
I'm sure that there is no bad blocks on SD.
I'll send any
From: David Howells <[EMAIL PROTECTED]>
Fix the /proc/pid/stat representation of executable boundaries. It should show
the bounds of the executable, but instead shows the bounds of the loader.
Before the patch is applied, the bug can be seen by examining, say, inetd:
# ps | grep inetd
On Thu, Mar 22, 2007 at 03:18:26AM -0800, Andrew Morton wrote:
> On Wed, 21 Mar 2007 13:22:17 -0700 Venkatesh Pallipadi <[EMAIL PROTECTED]>
> wrote:
>
> >
> > Introduce a new flag for timers - 'deferrable timer'
> > Timers that work normally when system is busy. But, will not cause CPU to
> >
Pavel Machek wrote:
> Hi!
>
> (Machine was suspended/resumed before this).
>
> mount /dev/mmc1 /mnt
>
Driver? Reproducable? Vanilla git kernel?
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainerhttp://www.kernel.org
PulseAudio, core developer
On Thu, Mar 22, 2007 at 09:09:42PM +1100, Rusty Russell wrote:
> My previous warning fix broke lguest if your text size wasn't correct
> to make the __start_paravirtprobe aligned correctly. Put the separate
> paravirtprobe section back, but inside the init section so it gets
> discarded.
>
> It
201 - 300 of 769 matches
Mail list logo
