> > Changelog since v1:
> > 1. Added a mutex to serialize directory creation/destruction for a user in
> >sysfs
> > 2. Added a spinlock in the task_group structure to serialize writes to
> >tg->shares.
> > 3. Removed /proc/root_user_cpu_shares.
> > 4. Added Documentation about the group
Hello all,
For accessing memory-mapped 64bit-BAR regions of a PCI card, the
respective BAR regions has to be made accessible to the kernel using
ioremap() function. Then readl()/writel() can be used on the address
returned by ioremap().
I am doing the similar steps to access the BARs of a card.
On Tue, 2 Oct 2007 23:26:42 +0200 Jean Delvare <[EMAIL PROTECTED]> wrote:
> On Mon, 1 Oct 2007 23:54:12 +0200, Jean Delvare wrote:
> > On Mon, 1 Oct 2007 22:54:47 +0200, Jean Delvare wrote:
> > > 2.6.23-rc8 and 2.6.23-rc8-git4 fail to build on one of my test
> > > machines, with:
> > >
> > >
On Thu, 4 Oct 2007 10:06:32 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > Huh? Isn't the block layer supposed to fill in the entire thing?
> > (i.e. current contents shouldn't matter)
>
> Yeah, but sg chaining requires that ->page be filled in
Hello list,
As i want lvm on drbd and drbd for the whole disk, exclusive /boot, i needed
to find a way to keep two nearly identical /etc-directories.
This lead to the idea to put the /etc-directory on a cd-rw and let / be
handled completely via drbd/lvm.
Because the /etc-files are only read
On Thursday 04 October 2007 00:53, Nick Piggin wrote:
> On Thursday 04 October 2007 16:37, gurudas pai wrote:
> > Hi,
> >
> > While running Oracle database test on x86/6GB RAM machine panics with
> > following messages.
>
> Hi,
>
> Hmm, seems like something in sys_remap_file_pages might have
On Thu, 4 Oct 2007, Mikael Pettersson wrote:
> On Wed, 3 Oct 2007 22:33:46 +0300, Riku Voipio wrote:
> > What's the state of this patch? I can confirm tst-robust1
> > from glibc testsuite locks a armv5 machine hard. With this patch
> > applied, the test succeeds.
>
> There were no comments from
On Thu, Oct 04 2007, Pierre Ossman wrote:
> On Thu, 4 Oct 2007 09:25:15 +0200
> Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> >
> > It looks like missing init of the sg list in mmc, does this work?
> >
>
> Huh? Isn't the block layer supposed to fill in the entire thing? (i.e.
> current contents
* Mike Kravetz <[EMAIL PROTECTED]> wrote:
> > if (rq->curr && p && rq && _need_resched())
> > trace_special_pid(p->pid, PRIO(p), PRIO(rq->curr));
>
> Not an issue with the patch, just that last bit of code pulled in for
> context. I don't think it is a bug, but the checking of
On Thu, 4 Oct 2007 09:25:15 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> It looks like missing init of the sg list in mmc, does this work?
>
Huh? Isn't the block layer supposed to fill in the entire thing? (i.e.
current contents shouldn't matter)
Rgds
Pierre
signature.asc
Description:
* Dhaval Giani <[EMAIL PROTECTED]> wrote:
> Hi Ingo,
>
> Can you please drop commit b1add858a10cece3a68b2d8cb9e7350843700a58 (last
> version of this patch) and try this instead?
> Changelog since v1:
> 1. Added a mutex to serialize directory creation/destruction for a user in
>sysfs
> 2.
On Wed, 3 Oct 2007 22:33:46 +0300, Riku Voipio wrote:
> What's the state of this patch? I can confirm tst-robust1
> from glibc testsuite locks a armv5 machine hard. With this patch
> applied, the test succeeds.
There were no comments from any Linux arch or futex maintainer.
Because of that I
* Dmitry Adamushko <[EMAIL PROTECTED]> wrote:
> results:
>
> (SCHED_FIFO)
>
> [EMAIL PROTECTED]:~/storage/prog$ sudo chrt -f 10 ./rr_interval
> time_slice: 0 : 0
>
> (SCHED_RR)
>
> [EMAIL PROTECTED]:~/storage/prog$ sudo chrt 10 ./rr_interval
> time_slice: 0 : 99984800
>
> (SCHED_NORMAL)
>
* Dmitry Adamushko <[EMAIL PROTECTED]> wrote:
> The following patch (sched: disable sleeper_fairness on SCHED_BATCH)
> seems to break GROUP_SCHED. Although, it may be 'oops'-less due to the
> possibility of 'p' being always a valid address.
thanks, applied.
Ingo
-
To unsubscribe from
Hi,
I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch, ),
and latest svn (3062) 0.7.X drbd.
After just 2 days of uptime, I did experience another crash.
I wonder if it is an XFS related bug, a DRBD one, or related to XFS on top of
DRBD.
This bug seems to occur with
On Wed, 3 Oct 2007 23:16:59 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <[EMAIL PROTECTED]> wrote:
>
> > OOPS followed by a 3 minute timeout, then completion of boot.
> > Not seen if card (Kingston microSD adapter) is ejected; not seen in
> >
On Thu, Oct 04 2007, FUJITA Tomonori wrote:
> On Wed, 3 Oct 2007 17:32:55 -0600
> "Patro, Sumant" <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > > -Original Message-
> > > From: FUJITA Tomonori [mailto:[EMAIL PROTECTED]
> > > Sent: Tuesday, October 02, 2007 5:01 PM
> > > To: [EMAIL
On Thursday 04 October 2007 16:37, gurudas pai wrote:
> Hi,
>
> While running Oracle database test on x86/6GB RAM machine panics with
> following messages.
Hi,
Hmm, seems like something in sys_remap_file_pages might have broken.
It's a bit hard to work out from the backtrace, though.
Is it
On Wed, Oct 03 2007, Andrew Morton wrote:
> On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <[EMAIL PROTECTED]> wrote:
>
> > OOPS followed by a 3 minute timeout, then completion of boot.
> > Not seen if card (Kingston microSD adapter) is ejected; not seen in
> > 2.6.23-rc8.
> > Running on a Dell
OOPS followed by a 3 minute timeout, then completion of boot.
Not seen if card (Kingston microSD adapter) is ejected; not seen in 2.6.23-rc8.
Running on a Dell XPS M1330 laptop.
`dmesg` reports:
[ 13.695045] mmcblk0: mmc0:e95c SD02G 1966080KiB
[ 13.695155] mmcblk0: p1
[ 13.706907] BUG:
Hi Kamalesh,
On 10/4/07, Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
> Kernel bug hit, while running fsstress over the CIFS mounted partition on
> the ppc64 machine
>
> cpu 0x0: Vector: 700 (Program Check) at [c00106ec75f0]
>
> pc: c00d69cc: .kmem_cache_free+0xac/0x154
>
> lr:
On Wed, Oct 03, 2007 at 10:40:25PM -0400, Casey Dahlin wrote:
> From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
> From: Casey Dahlin <[EMAIL PROTECTED]>
> Date: Wed, 3 Oct 2007 22:01:49 -0400
> Subject: [PATCH] Code style fix for open_exec
>
> Fix a horribly mangled 5 level
Hi,
Kernel bug hit, while running fsstress over the CIFS mounted partition on
the ppc64 machine
cpu 0x0: Vector: 700 (Program Check) at [c00106ec75f0]
pc: c00d69cc: .kmem_cache_free+0xac/0x154
lr: c00b05f0: .mempool_free_slab+0x1c/0x30
sp: c00106ec7870
On Wed, 03 Oct 2007 19:41:16 -0400
Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> We also have the 64-bit inode support from RedHat/Peter Staubach.
>
As has been pointed[1] out[2], this will cause regressions for non-LFS
applications (of which there are still lots and lots). This change
should
On Thu, Oct 04, 2007 at 01:50:36AM -0400, Theodore Ts'o wrote:
> From: Mingming Cao <[EMAIL PROTECTED]>
>
> JBD: Replace slab allocations with page cache allocations
It's page allocations, not page cache allocations.
> Also this patch cleans up jbd_kmalloc and replace it with kmalloc directly
On Wed, Oct 03 2007, Grant Likely wrote:
> Jens,
>
> Here are some more Sysace patches based on comments received on the
> first series and a run through sparse. Can you please queue them up
> for 2.6.24?
Applied all 3, looked fine to me.
--
Jens Axboe
-
To unsubscribe from this list: send
On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis <[EMAIL PROTECTED]> wrote:
> OOPS followed by a 3 minute timeout, then completion of boot.
> Not seen if card (Kingston microSD adapter) is ejected; not seen in
> 2.6.23-rc8.
> Running on a Dell XPS M1330 laptop.
>
> `dmesg` reports:
>
> [
On Thu, Oct 04, 2007 at 01:59:28AM -0400, Theodore Ts'o wrote:
>
> I've just released the 2.6.23-rc9-ext4-1.
Whoops, I obviously screwed up the subject in my announcement e-mail.
Sorry about that!
- Ted
-
To unsubscribe from this list:
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext3_next_entry() when
I've just released the 2.6.23-rc9-ext4-1. It collapses some patches in
preparation for pushing them to Linus, and adds some of cleanup patches
that had been incorporated into Andrew's broken-out-2007-10-01-04-09
series. It also has some new development patches in the unstable (not
yet ready to
From: Coly Li <[EMAIL PROTECTED]>
implement in future. Therefore fragment related source code in ext4 should
be obsoleted -- no one will use it.
This patch obsolete fragment from ext4. Another patch posted on linux-ext4
removing fragment supporting from e2fsprogs.
Signed-off-by: Coly Li
From: Jose R. Santos <[EMAIL PROTECTED]>
data is located within the storage media. This allows for the allocation
of bitmaps or inode tables outside the block group boundaries in cases
where bad blocks forces us to look for new blocks which the owning block
group can not satisfy. This will also
From: Andreas Dilger <[EMAIL PROTECTED]>
In pass1 of e2fsck, every inode table in the fileystem is scanned and checked,
regardless of whether it is in use. This is this the most time consuming part
of the filesystem check. The unintialized block group feature can greatly
reduce e2fsck time by
From: Eric Sandeen <[EMAIL PROTECTED]>
CONFIG_EXT4_INDEX is not an exposed config option in the kernel, and it is
unconditionally defined in ext4_fs.h. tune2fs is already able to turn off
dir indexing, so at this point it's just cluttering up the code. Remove
it.
Signed-off-by: Eric Sandeen
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext3
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext3 without some changes to the directory handling
code. The reason is that an empty 64kB directory block
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk.
Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
Signed-off-by:
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext4,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext4 without some changes to the directory handling
code. The reason is that an empty 64kB directory block
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext2,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext2 without some changes to the directory handling
code. The reason is that an empty 64kB directory block
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext4_next_entry() when
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/fsync.c |2 +-
fs/ext4/inode.c |2 +-
fs/ext4/xattr.c |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
index
From: Jose R. Santos <[EMAIL PROTECTED]>
Mostly stolen from akpm's JBD cleanup patch.
- use `#ifdef foo' instead of `#if defined(foo)'
- Make journal_enable_debug __read_mostly just for the heck of it
- Make jbd_debugfs_dir and jbd_debug static
- debugfs_remove(NULL) is legal: remove unneeded
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent.ee_start to ext4_extent.ee_start_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_r_blocks_count and s_free_blocks_count to
s_r_blocks_count_lo and s_free_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_block_bitmap to bg_block_bitmap_lo
This helps in catching some BUGS due to direct
partial access of these split fields.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c |6 +++---
include/linux/ext4_fs.h |
The following ext4 patches are planned for submission to Linus once
the merge window for 2.6.24-rc1 is opened.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
fs/ext4/inode.c |6 --
include/linux/ext4_fs.h | 14 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_blocks_count to s_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c
From: Jan Kara <[EMAIL PROTECTED]>
We should really call journal_abort() and not __journal_abort_hard() in
case of errors. The latter call does not record the error in the journal
superblock and thus filesystem won't be marked as with errors later (and
user could happily mount it without any
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent_idx.ei_leaf ext4_extent_idx.ei_leaf_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/extents.c |4 ++--
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_inode_bitmap and bg_inode_table to bg_inode_bitmap_lo
and bg_inode_table_lo. This helps in finding BUGs due to
direct partial access of these split 64 bit values
Also fix one direct partial access
Signed-off-by: Aneesh Kumar K.V <[EMAIL
From: Mingming Cao <[EMAIL PROTECTED]>
JBD: Replace slab allocations with page cache allocations
JBD allocate memory for committed_data and frozen_data from slab. However
JBD should not pass slab pages down to the block layer. Use page allocator
pages instead. This will also prepare JBD for the
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert bg_inode_bitmap and bg_inode_table to bg_inode_bitmap_lo
and bg_inode_table_lo. This helps in finding BUGs due to
direct partial access of these split 64 bit values
Also fix one direct partial access
Signed-off-by: Aneesh Kumar K.V [EMAIL
From: Mingming Cao [EMAIL PROTECTED]
JBD: Replace slab allocations with page cache allocations
JBD allocate memory for committed_data and frozen_data from slab. However
JBD should not pass slab pages down to the block layer. Use page allocator
pages instead. This will also prepare JBD for the
From: Jan Kara [EMAIL PROTECTED]
We should really call journal_abort() and not __journal_abort_hard() in
case of errors. The latter call does not record the error in the journal
superblock and thus filesystem won't be marked as with errors later (and
user could happily mount it without any
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert ext4_extent_idx.ei_leaf ext4_extent_idx.ei_leaf_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values.
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
fs/ext4/extents.c |4 ++--
The following ext4 patches are planned for submission to Linus once
the merge window for 2.6.24-rc1 is opened.
- Ted
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
Signed-off-by: Andrew Morton [EMAIL PROTECTED]
---
fs/ext4/inode.c |6 --
include/linux/ext4_fs.h | 14 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert s_blocks_count to s_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
fs/ext4/super.c |
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert s_r_blocks_count and s_free_blocks_count to
s_r_blocks_count_lo and s_free_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh
On Thu, Oct 04, 2007 at 01:59:28AM -0400, Theodore Ts'o wrote:
I've just released the 2.6.23-rc9-ext4-1.
Whoops, I obviously screwed up the subject in my announcement e-mail.
Sorry about that!
- Ted
-
To unsubscribe from this list:
On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis [EMAIL PROTECTED] wrote:
OOPS followed by a 3 minute timeout, then completion of boot.
Not seen if card (Kingston microSD adapter) is ejected; not seen in
2.6.23-rc8.
Running on a Dell XPS M1330 laptop.
`dmesg` reports:
[ 13.695045]
From: Jan Kara [EMAIL PROTECTED]
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext3_next_entry() when we
From: Jose R. Santos [EMAIL PROTECTED]
data is located within the storage media. This allows for the allocation
of bitmaps or inode tables outside the block group boundaries in cases
where bad blocks forces us to look for new blocks which the owning block
group can not satisfy. This will also
From: Andreas Dilger [EMAIL PROTECTED]
In pass1 of e2fsck, every inode table in the fileystem is scanned and checked,
regardless of whether it is in use. This is this the most time consuming part
of the filesystem check. The unintialized block group feature can greatly
reduce e2fsck time by
From: Jan Kara [EMAIL PROTECTED]
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk.
Signed-off-by: Jan Kara [EMAIL PROTECTED]
Signed-off-by: Mingming
From: Takashi Sato [EMAIL PROTECTED]
This patch set supports large block size(4k, =64k) in ext4,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext4 without some changes to the directory handling
code. The reason is that an empty 64kB directory block would
From: Jan Kara [EMAIL PROTECTED]
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext4_next_entry() when we
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
fs/ext4/fsync.c |2 +-
fs/ext4/inode.c |2 +-
fs/ext4/xattr.c |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
index
From: Jose R. Santos [EMAIL PROTECTED]
Mostly stolen from akpm's JBD cleanup patch.
- use `#ifdef foo' instead of `#if defined(foo)'
- Make journal_enable_debug __read_mostly just for the heck of it
- Make jbd_debugfs_dir and jbd_debug static
- debugfs_remove(NULL) is legal: remove unneeded
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert bg_block_bitmap to bg_block_bitmap_lo
This helps in catching some BUGS due to direct
partial access of these split fields.
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
fs/ext4/super.c |6 +++---
include/linux/ext4_fs.h |2
From: Aneesh Kumar K.V [EMAIL PROTECTED]
Convert ext4_extent.ee_start to ext4_extent.ee_start_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
From: Takashi Sato [EMAIL PROTECTED]
This patch set supports large block size(4k, =64k) in ext2,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext2 without some changes to the directory handling
code. The reason is that an empty 64kB directory block would
From: Eric Sandeen [EMAIL PROTECTED]
CONFIG_EXT4_INDEX is not an exposed config option in the kernel, and it is
unconditionally defined in ext4_fs.h. tune2fs is already able to turn off
dir indexing, so at this point it's just cluttering up the code. Remove
it.
Signed-off-by: Eric Sandeen
From: Takashi Sato [EMAIL PROTECTED]
This patch set supports large block size(4k, =64k) in ext3
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext3 without some changes to the directory handling
code. The reason is that an empty 64kB directory block would
From: Coly Li [EMAIL PROTECTED]
implement in future. Therefore fragment related source code in ext4 should
be obsoleted -- no one will use it.
This patch obsolete fragment from ext4. Another patch posted on linux-ext4
removing fragment supporting from e2fsprogs.
Signed-off-by: Coly Li [EMAIL
I've just released the 2.6.23-rc9-ext4-1. It collapses some patches in
preparation for pushing them to Linus, and adds some of cleanup patches
that had been incorporated into Andrew's broken-out-2007-10-01-04-09
series. It also has some new development patches in the unstable (not
yet ready to
On Wed, Oct 03 2007, Grant Likely wrote:
Jens,
Here are some more Sysace patches based on comments received on the
first series and a run through sparse. Can you please queue them up
for 2.6.24?
Applied all 3, looked fine to me.
--
Jens Axboe
-
To unsubscribe from this list: send the
On Wed, 03 Oct 2007 19:41:16 -0400
Trond Myklebust [EMAIL PROTECTED] wrote:
We also have the 64-bit inode support from RedHat/Peter Staubach.
As has been pointed[1] out[2], this will cause regressions for non-LFS
applications (of which there are still lots and lots). This change
should be
On Thu, Oct 04, 2007 at 01:50:36AM -0400, Theodore Ts'o wrote:
From: Mingming Cao [EMAIL PROTECTED]
JBD: Replace slab allocations with page cache allocations
It's page allocations, not page cache allocations.
Also this patch cleans up jbd_kmalloc and replace it with kmalloc directly
That
Hi,
Kernel bug hit, while running fsstress over the CIFS mounted partition on
the ppc64 machine
cpu 0x0: Vector: 700 (Program Check) at [c00106ec75f0]
pc: c00d69cc: .kmem_cache_free+0xac/0x154
lr: c00b05f0: .mempool_free_slab+0x1c/0x30
sp: c00106ec7870
On Wed, Oct 03, 2007 at 10:40:25PM -0400, Casey Dahlin wrote:
From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
From: Casey Dahlin [EMAIL PROTECTED]
Date: Wed, 3 Oct 2007 22:01:49 -0400
Subject: [PATCH] Code style fix for open_exec
Fix a horribly mangled 5 level indent
Hi Kamalesh,
On 10/4/07, Kamalesh Babulal [EMAIL PROTECTED] wrote:
Kernel bug hit, while running fsstress over the CIFS mounted partition on
the ppc64 machine
cpu 0x0: Vector: 700 (Program Check) at [c00106ec75f0]
pc: c00d69cc: .kmem_cache_free+0xac/0x154
lr:
OOPS followed by a 3 minute timeout, then completion of boot.
Not seen if card (Kingston microSD adapter) is ejected; not seen in 2.6.23-rc8.
Running on a Dell XPS M1330 laptop.
`dmesg` reports:
[ 13.695045] mmcblk0: mmc0:e95c SD02G 1966080KiB
[ 13.695155] mmcblk0: p1
[ 13.706907] BUG:
On Wed, Oct 03 2007, Andrew Morton wrote:
On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis [EMAIL PROTECTED] wrote:
OOPS followed by a 3 minute timeout, then completion of boot.
Not seen if card (Kingston microSD adapter) is ejected; not seen in
2.6.23-rc8.
Running on a Dell XPS M1330
On Thursday 04 October 2007 16:37, gurudas pai wrote:
Hi,
While running Oracle database test on x86/6GB RAM machine panics with
following messages.
Hi,
Hmm, seems like something in sys_remap_file_pages might have broken.
It's a bit hard to work out from the backtrace, though.
Is it possible
On Thu, Oct 04 2007, FUJITA Tomonori wrote:
On Wed, 3 Oct 2007 17:32:55 -0600
Patro, Sumant [EMAIL PROTECTED] wrote:
-Original Message-
From: FUJITA Tomonori [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 02, 2007 5:01 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL
On Wed, 3 Oct 2007 23:16:59 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
On Wed, 03 Oct 2007 23:11:02 -0700 Don Mullis [EMAIL PROTECTED] wrote:
OOPS followed by a 3 minute timeout, then completion of boot.
Not seen if card (Kingston microSD adapter) is ejected; not seen in
2.6.23-rc8.
Hi,
I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch, ),
and latest svn (3062) 0.7.X drbd.
After just 2 days of uptime, I did experience another crash.
I wonder if it is an XFS related bug, a DRBD one, or related to XFS on top of
DRBD.
This bug seems to occur with
* Dmitry Adamushko [EMAIL PROTECTED] wrote:
The following patch (sched: disable sleeper_fairness on SCHED_BATCH)
seems to break GROUP_SCHED. Although, it may be 'oops'-less due to the
possibility of 'p' being always a valid address.
thanks, applied.
Ingo
-
To unsubscribe from this
* Dmitry Adamushko [EMAIL PROTECTED] wrote:
results:
(SCHED_FIFO)
[EMAIL PROTECTED]:~/storage/prog$ sudo chrt -f 10 ./rr_interval
time_slice: 0 : 0
(SCHED_RR)
[EMAIL PROTECTED]:~/storage/prog$ sudo chrt 10 ./rr_interval
time_slice: 0 : 99984800
(SCHED_NORMAL)
[EMAIL
On Wed, 3 Oct 2007 22:33:46 +0300, Riku Voipio wrote:
What's the state of this patch? I can confirm tst-robust1
from glibc testsuite locks a armv5 machine hard. With this patch
applied, the test succeeds.
There were no comments from any Linux arch or futex maintainer.
Because of that I intend
* Dhaval Giani [EMAIL PROTECTED] wrote:
Hi Ingo,
Can you please drop commit b1add858a10cece3a68b2d8cb9e7350843700a58 (last
version of this patch) and try this instead?
Changelog since v1:
1. Added a mutex to serialize directory creation/destruction for a user in
sysfs
2. Added a
On Thu, 4 Oct 2007 09:25:15 +0200
Jens Axboe [EMAIL PROTECTED] wrote:
It looks like missing init of the sg list in mmc, does this work?
Huh? Isn't the block layer supposed to fill in the entire thing? (i.e.
current contents shouldn't matter)
Rgds
Pierre
signature.asc
Description: PGP
* Mike Kravetz [EMAIL PROTECTED] wrote:
if (rq-curr p rq _need_resched())
trace_special_pid(p-pid, PRIO(p), PRIO(rq-curr));
Not an issue with the patch, just that last bit of code pulled in for
context. I don't think it is a bug, but the checking of 'rq' after
On Thu, Oct 04 2007, Pierre Ossman wrote:
On Thu, 4 Oct 2007 09:25:15 +0200
Jens Axboe [EMAIL PROTECTED] wrote:
It looks like missing init of the sg list in mmc, does this work?
Huh? Isn't the block layer supposed to fill in the entire thing? (i.e.
current contents shouldn't
On Thu, 4 Oct 2007, Mikael Pettersson wrote:
On Wed, 3 Oct 2007 22:33:46 +0300, Riku Voipio wrote:
What's the state of this patch? I can confirm tst-robust1
from glibc testsuite locks a armv5 machine hard. With this patch
applied, the test succeeds.
There were no comments from any Linux
On Thursday 04 October 2007 00:53, Nick Piggin wrote:
On Thursday 04 October 2007 16:37, gurudas pai wrote:
Hi,
While running Oracle database test on x86/6GB RAM machine panics with
following messages.
Hi,
Hmm, seems like something in sys_remap_file_pages might have broken.
It's a
Hello list,
As i want lvm on drbd and drbd for the whole disk, exclusive /boot, i needed
to find a way to keep two nearly identical /etc-directories.
This lead to the idea to put the /etc-directory on a cd-rw and let / be
handled completely via drbd/lvm.
Because the /etc-files are only read
On Thu, 4 Oct 2007 10:06:32 +0200
Jens Axboe [EMAIL PROTECTED] wrote:
On Thu, Oct 04 2007, Pierre Ossman wrote:
Huh? Isn't the block layer supposed to fill in the entire thing?
(i.e. current contents shouldn't matter)
Yeah, but sg chaining requires that -page be filled in properly or
On Tue, 2 Oct 2007 23:26:42 +0200 Jean Delvare [EMAIL PROTECTED] wrote:
On Mon, 1 Oct 2007 23:54:12 +0200, Jean Delvare wrote:
On Mon, 1 Oct 2007 22:54:47 +0200, Jean Delvare wrote:
2.6.23-rc8 and 2.6.23-rc8-git4 fail to build on one of my test
machines, with:
401 - 500 of 902 matches
Mail list logo