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:
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.
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 scheduler.
On Tue, 2007-10-02 at 19:30 +0800, Kalle Pokki wrote:
The Blackfin Ethernet MAC driver does not compile. It seems the driver
is
missing some pinmux defines.
CC drivers/net/bfin_mac.o
drivers/net/bfin_mac.c: In function 'setup_pin_mux':
drivers/net/bfin_mac.c:275: error: 'P_MII0'
On Thursday 04 October 2007 05:59, Christoph Lameter wrote:
Make the stack size configurable now that we can fallback to vmalloc if
necessary. SGI NUMA configurations may need more stack because cpumasks
and nodemasks are at times kept on the stack. With the coming 16k cpu
support
Hmm, I
On 10/3/2007 11:58 PM, Eric W. Biederman wrote:
Right. And INTx has such a pending bit as well. I guess I figured
if MSI was enabled transferring it over would be the obvious thing to
do.
The INTx pending and disable bit were only added starting with PCI 2.3,
so in PCI-2.2 and PCI-X
From: Josef Whiter [EMAIL PROTECTED]
If a glock is in the exclusive state and a request for demote to
deferred has been received, then further requests for demote to
shared are being ignored. This patch fixes that by ensuring that
we demote to unlocked in that case.
Signed-off-by: Josef Whiter
Matt Mackall wrote:
On Wed, Oct 03, 2007 at 06:20:43PM +0400, Pavel Emelyanov wrote:
Just make the __pid_nr() etc functions that expect the argument
to always be not NULL.
Signed-off-by: Pavel Emelyanov [EMAIL PROTECTED]
static inline pid_t pid_nr(struct pid *pid)
{
pid_t nr = 0;
Randy Dunlap wrote:
On Wed, 03 Oct 2007 18:19:01 +0400 Pavel Emelyanov wrote:
This is a pid which is attached to tasks when they detach
their pids. This is done in detach_pid() and transfer_pid().
The pid_alive() check is changed to reflect this fact.
Signed-off-by: Pavel Emelyanov [EMAIL
On Wednesday 03 October 2007 18:58, Chuck Ebbert wrote:
On 10/03/2007 12:10 AM, H. Peter Anvin wrote:
Randy Dunlap wrote:
Maybe we can/should merge the doc files along with the x86 arch merge.
Well, the x86 merge is pretty much mechanical. It should be followed up
with a lot of manual
Hi,
Since it seems that another merge window will probably be opening shortly
this is a posting of the current content of the GFS2/DLM -nmw git tree.
There are no new features this time, its all fixes and cleanups. I have
a few patches that I'm holding back which I'm intending to start off
the
From: Steven Whitehouse [EMAIL PROTECTED]
One of the races relates to referencing a variable while not holding
its protecting spinlock. The patch simply moves the test inside the
spin lock. The other races occurs when a demote to unlocked request
occurs during the time a demote to shared request
From: Steven Whitehouse [EMAIL PROTECTED]
This fixes an oops which was occurring during glock dumping due to the
seq file code not taking a reference to the glock. Also this fixes a
memory leak which occurred in certain cases, in turn preventing the
filesystem from unmounting.
Signed-off-by:
From: Jesper Juhl [EMAIL PROTECTED]
This patch cleans up duplicate includes in
fs/gfs2/
Signed-off-by: Jesper Juhl [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
index 6b6ae45..d403fd7 100644
--- a/fs/gfs2/glock.c
+++
From: Bob Peterson [EMAIL PROTECTED]
This is the first of five patches for bug #248176:
There were still some critical variables being manipulated outside
the log_lock spinlock. That usually resulted in a hang.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse
From: Bob Peterson [EMAIL PROTECTED]
This is patch 2 of 5 for bug #248176.
The list_move code previously concocted in log.c for bug #238162
(see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=238162#c23)
never runs as bh can now never be NULL at this point.
Signed-off-by: Bob Peterson
From: Bob Peterson [EMAIL PROTECTED]
This is patch three of five for bug #248176.
The try_rgrp_unlink code in rgrp.c had an infinite loop. This was
caused because the bitmap function rgblk_search can return a block
less than the goal block, in which case it was looping. The fix is
to make it
From: Denis Cheng [EMAIL PROTECTED]
this is more clear.
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: David Teigland [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/locking/dlm/plock.c b/fs/gfs2/locking/dlm/plock.c
index fba1f1d..1f7b038
From: Bob Peterson [EMAIL PROTECTED]
This is patch 5 of 5 for bug #248176
Metadata corruption was occurring because page references weren't
being removed in all cases. I previously added a function called
detach_bufdata, but I discovered there already WAS a function out
there to do the job.
From: Denis Cheng [EMAIL PROTECTED]
these struct *_operations are all method tables, thus should be const.
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/eaops.c b/fs/gfs2/eaops.c
index 1ab3e9d..aa8dbf3 100644
---
From: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index cf5aa50..9a5e840 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -28,6 +28,7 @@
From: Steven Whitehouse [EMAIL PROTECTED]
We only need a single gfs2_scand process rather than the one
per filesystem which we had previously. As a result the parameter
determining the frequency of gfs2_scand runs becomes a module
parameter rather than a mount parameter as it was before.
From: Bob Peterson [EMAIL PROTECTED]
This is for bugzilla bug #248176: GFS2: invalid metadata block
Patches 1 thru 3 were accepted upstream, but there were problems
with 4 and 5. Those issues have been resolved and now the recovery
tests are passing without errors. This code has gone through
From: Bob Peterson [EMAIL PROTECTED]
This is for bugzilla bug #248176: GFS2: invalid metadata block
Patches 1 thru 3 were accepted upstream, but there were problems
with 4 and 5. Those issues have been resolved and now the recovery
tests are passing without errors. This code has gone through
From: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index f0bcaa2..32b2859 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -808,7 +808,6 @@
From: Denis Cheng [EMAIL PROTECTED]
sb-s_fs_info is a void pointer, thus the type cast is not needed.
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index 32b2859..25cfab9 100644
---
From: Denis Cheng [EMAIL PROTECTED]
the original code could work, but I think this code could work better.
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index 25cfab9..6c820cb 100644
---
From: Abhijith Das [EMAIL PROTECTED]
This patch forcibly unstuffs (if stuffed) the hidden quota inode at the
first availble opportunity. In any practical scenario the quota inode
won't be stuffed, so this is ok to do. Unstuffing the quota inode allows
us to ignore the case of a stuffed quota
From: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Denis Cheng [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index 6c820cb..c1c6672 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -292,8 +292,9 @@
From: Abhijith Das [EMAIL PROTECTED]
This is the filesystem part of the patches to fix this bz. There are
additional userland patches (gfs2_quota, libgfs2) for the complete
solution. This patch adds a new field qu_ll_next to the gfs2_quota
structure. This field allows us to create linked lists of
From: Steven Whitehouse [EMAIL PROTECTED]
This patch fixes some bugs relating to journaled data files by cleaning
up the gfs2_invalidatepage() and gfs2_releasepage() functions. We now
never block during gfs2_releasepage(), instead we always either release
or refuse to release depending on the
From: Steven Whitehouse [EMAIL PROTECTED]
This was missing from the dir_split_leaf() function although in
most cases its not a problem due to other functions having
already previously called gfs2_trans_add_bh. This makes certain
that it is correct.
Signed-off-by: Steven Whitehouse [EMAIL
From: Benjamin Marzinski [EMAIL PROTECTED]
match_token() was returning garbage data instead of a fail value. This data
happened to match a valid option id for an option that required an argument (in
this case, lockproto=%s) For match_token() to correctly fail if the option
doesn't match any of
From: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
index 1e56f4d..93fa427 100644
--- a/fs/gfs2/bmap.c
+++ b/fs/gfs2/bmap.c
@@ -93,10 +93,10 @@ static int
From: Steven Whitehouse [EMAIL PROTECTED]
The following patch removes the ordered write processing from
databuf_lo_before_commit() and moves it to log.c. This has the effect of
greatly simplyfying databuf_lo_before_commit() and well as potentially
making the ordered write code more efficient.
As
From: Steven Whitehouse [EMAIL PROTECTED]
This collects together the operations required to remove a gfs2_bufdata
from the ail lists. Its only called from two places to start with, but
expect to see more of this function in future.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git
From: Abhijith Das [EMAIL PROTECTED]
When you try to mount gfs2 with -o garbage, the mount fails and the gfs2
superblock is deallocated and becomes NULL. The vfs comes around later
on and calls gfs2_kill_sb. At this point the hidden gfs2 superblock
pointer (sb-s_fs_info) is NULL and dereferencing
From: Bob Peterson [EMAIL PROTECTED]
This is a patch to GFS2 to protect sd_log_num_jdata with the
gfs2_log_lock. Without this patch, there is a timing window
where you can get hit the following assert from function
gfs2_log_flush():
gfs2_assert_withdraw(sdp,
From: Abhijith Das [EMAIL PROTECTED]
With this patch, gfs2 glockdump through the debugfs filesystem will only
dump glocks for the specified filesystem instead of all glocks. Also, to
aid debugging, the glock number is dumped in hex instead of decimal.
Signed-off-by: Steven Whitehouse [EMAIL
From: Steve French [EMAIL PROTECTED]
When looking at an unrelated problem, I noticed that nfsd does not
set nameidata pointer on create (ie nd is NULL). This should
cause an oops in some cases in which when NFSd is mounted over GFS2.
Signed-off-by: Steve French [EMAIL PROTECTED]
Signed-off-by:
From: Patrick Caulfield [EMAIL PROTECTED]
This patch fixes the slight mess made in lowcomms closing by previous patches
and fixes all sorts of DLM hangs.
Signed-Off-By: Patrick Caulfield [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/dlm/lowcomms.c
From: Wendy Cheng [EMAIL PROTECTED]
Current GFS2 setattr call unconditionally invokes do_shrink even the
requested size and actual file size are equal. This has generated large
amount of extra IOs found during NFS benchmark runs. This patch moves
the relevant logic out of shrink code path. Since
From: Benjamin Marzinski [EMAIL PROTECTED]
When a lot of IO, with some distributed mmap IO, is run on a GFS2 filesystem in
a cluster, it will deadlock. The reason is that do_no_page() will repeatedly
call gfs2_sharewrite_nopage(), because each node keeps giving up the glock
too early, and is
From: Wendy Cheng [EMAIL PROTECTED]
Fix a nasty inode meta data corruption issue by keeping the buffer head in
icache array. This buffer needs to stay in memory until journal flush occurs
Otherwise, gfs2_meta_inode_buffer could do a disk read before the inode hits
disk. It ends up with meta data
From: Steven Whitehouse [EMAIL PROTECTED]
This patch corrects the lock ordering in unlink to be the same as
that in the rest of GFS2, i.e. parent - child - rgrp.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_inode.c b/fs/gfs2/ops_inode.c
index 5b8b994..2cbe5a3
From: Steven Whitehouse [EMAIL PROTECTED]
Journaled data is marked dirty by gfs2_unpin and should not be marked
dirty here.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
index 9b89904..1e56f4d 100644
--- a/fs/gfs2/bmap.c
+++ b/fs/gfs2/bmap.c
@@
From: Steven Whitehouse [EMAIL PROTECTED]
gfs2_pin and gfs2_unpin are only used in lops.c, despite being
defined in meta_io.c, so this patch moves them into lops.c and
makes them static. At the same time, its possible to clean up
the locking in the buf and databuf _lo_add() functions so that
we
From: Steven Whitehouse [EMAIL PROTECTED]
Both the revoke structure and the bufdata structure are quite similar.
They are basically small tags which are put on lists. In addition to
which the revoke structure is always allocated when there is a bufdata
structure which is (or can be) freed. As
Remove NULL initializers and clean whitespace a bit.
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
diff --git a/drivers/char/lp.c b/drivers/char/lp.c
index 62051f8..8267ff8 100644
--- a/drivers/char/lp.c
+++ b/drivers/char/lp.c
@@ -144,7 +144,7 @@ static unsigned int lp_count = 0;
static struct
On Wed, Oct 03, 2007 at 04:41:37PM +0100, Adrian McMenamin wrote:
On Wed, October 3, 2007 7:18 am, Paul Mundt wrote:
On Tue, Oct 02, 2007 at 10:09:27PM +0100, Adrian McMenamin wrote:
Fix SH DMAC code to correctly handle PVR2 cascade DMA.
This updates http://lkml.org/lkml/2007/10/2/276
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 you can strace to find the arguments for the
On Thu, 4 Oct 2007, Pavel Machek wrote:
-On powererpc systems when a soft-reset is generated, die() is called by all
cpus
+On powerpc systems when a soft-reset is generated, die() is called by all
cpus
^^^
i
1 - 100 of 902 matches
Mail list logo
