From: Christian Borntraeger <[EMAIL PROTECTED]>
ext_int_info_t is no longer used in entry(64).S Instead do_extint is a C
function that handles the hash search.
As the structure is handled in C code, we can also remove the packed
attribute to avoid alignment issues. (Currently there is no
From: Heiko Carstens <[EMAIL PROTECTED]>
Also removes a bunch of ^L in drivers/s390/cio/cmf.c
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
arch/s390/kernel/audit.c|7 +--
arch/s390/kernel/audit.h| 15
From: Heiko Carstens <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
drivers/s390/crypto/zcrypt_mono.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: quilt-2.6/drivers/s390/crypto/zcrypt_mono.c
From: Martin Schwidefsky <[EMAIL PROTECTED]>
The termination condition of the loop that prints the operands of
an instruction doesn't stop after the maximum of 6 operands.
It continues with the operands of the next instruction format
instead which create really long lines.
Signed-off-by: Martin
From: Cornelia Huck <[EMAIL PROTECTED]>
Don't forget to set dev->groups for early ccw devices like the
console device so the default attributes are created.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
drivers/s390/cio/device.c |
From: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
Documentation/s390/00-INDEX |2 -
Documentation/s390/CommonIO | 51 +---
Documentation/s390/cds.txt |
From: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
---
Documentation/s390/00-INDEX | 26 ++
1 file changed, 26 insertions(+)
Index: quilt-2.6/Documentation/s390/00-INDEX
From: Cornelia Huck <[EMAIL PROTECTED]>
Disable channel measurements for all ccw devices via the ccw bus's
shutdown method. Clear residual cmf related information that may be
in the schib when setting up a new subchannel.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin
From: Cornelia Huck <[EMAIL PROTECTED]>
Comment a bunch of function in docbook style and convert existing
comments on structures to docbook.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
From: Cornelia Huck <[EMAIL PROTECTED]>
s390-drivers is generated using the docbook comments. It should
eventually supersede Documentation/s390/cds.txt.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL
From: Cornelia Huck <[EMAIL PROTECTED]>
Fix some formatting and correct a comment.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
---
drivers/s390/cio/cmf.c | 141
From: Cornelia Huck <[EMAIL PROTECTED]>
subchannel_add_files() no longer exists, remove from header.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
---
drivers/s390/cio/css.h |1 -
1
From: Cornelia Huck <[EMAIL PROTECTED]>
- Fix existing kerneldoc-style comments.
- Move descriptions of functions from cmb.h to cmf.c.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
---
The current set of s390 patches ready to be pushed once 2.6.23
has hit the streets.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
From: Cornelia Huck <[EMAIL PROTECTED]>
Rename css[] to channel_subsystems[] to avoid name clashes.
Signed-off-by: Cornelia Huck <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
Signed-off-by: Heiko Carstens <[EMAIL PROTECTED]>
---
drivers/s390/cio/chp.c| 14
Mikael Pettersson wrote::
On Wed, 03 Oct 2007 17:06:24 +0900, Shi Weihua wrote:
Fixing alternative signal stack wraparound.
If a process uses alternative signal stack by using sigaltstack()
and that stack overflow, stack wraparound occurs.
This patch checks whether the signal frame is on the
On Thu, Oct 04 2007, FUJITA Tomonori wrote:
> On Thu, 4 Oct 2007 12:48:58 +0200
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Oct 04, 2007 at 09:28:34AM +0200, Jens Axboe wrote:
> > >...
> > > Tomo, this is the patch I added.
> >
> > Please excuse my comment in case this was already
On Thu, Oct 04 2007, Pierre Ossman wrote:
> On Thu, 4 Oct 2007 12:38:05 +0200
> Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Oct 04 2007, Pierre Ossman wrote:
> > >
> > > Is that a yes or a no? You said that the ->page field was involved
> > > in
> >
> > It's a conditional yes, re-read
On Thu, 4 Oct 2007 12:48:58 +0200
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04, 2007 at 09:28:34AM +0200, Jens Axboe wrote:
> >...
> > Tomo, this is the patch I added.
>
> Please excuse my comment in case this was already clear:
>
> You are aware that this bug is a regression in
On Thu, Oct 04, 2007 at 09:28:34AM +0200, Jens Axboe wrote:
>...
> Tomo, this is the patch I added.
Please excuse my comment in case this was already clear:
You are aware that this bug is a regression in 2.6.23-rc and the patch
should therefore go to Linus ASAP and not after the release of
On Thu, 4 Oct 2007 12:38:05 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > Is that a yes or a no? You said that the ->page field was involved
> > in
>
> It's a conditional yes, re-read it :-)
>
I didn't get the memo about what chained sg
On Thu, Oct 04 2007, Pierre Ossman wrote:
> On Thu, 4 Oct 2007 11:30:14 +0200
> Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Oct 04 2007, Pierre Ossman wrote:
> > >
> > > I assume sg_init_one() still can work on an uninitialized sg entry?
> >
> > Yes, but only if that sg entry is not
On Thu, Oct 04 2007, FUJITA Tomonori wrote:
> On Thu, 4 Oct 2007 09:28:34 +0200
> Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Oct 04 2007, FUJITA Tomonori wrote:
> > > On Wed, 3 Oct 2007 17:32:55 -0600
> > > "Patro, Sumant" <[EMAIL PROTECTED]> wrote:
> > >
> > > >
> > > >
> > > > >
On Thu, 4 Oct 2007 11:30:14 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Thu, Oct 04 2007, Pierre Ossman wrote:
> >
> > I assume sg_init_one() still can work on an uninitialized sg entry?
>
> Yes, but only if that sg entry is not part of a chained list.
>
Is that a yes or a no? You said
On Thu, 4 Oct 2007 09:28:34 +0200
Jens Axboe <[EMAIL PROTECTED]> wrote:
> 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
On Thu 2007-10-04 11:51:35, Jan Engelhardt wrote:
>
> On Oct 4 2007 11:44, Pavel Machek wrote:
> >diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
> >index 7f1730f..1595a45 100644
> >--- a/Documentation/CodingStyle
> >+++ b/Documentation/CodingStyle
> >@@ -71,6 +71,15 @@ used
Hi,
I am using buildroot to build toolchain (GCC ver
3.4.3, binutil-1.15 and ucLibc-0.9.28, linux-2.6.18
kernel) for MIPS processor with soft float option
enabled.
I have written a loadble module ( which gets complied
along with kernel) which does some floating point
operation.
When i try to
On Thu 2007-10-04 06:04:09, Robert P. J. Day wrote:
> 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
>
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
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
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
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
Paul M,
This snippet from the memory allocation hot path worries me a bit.
Once per memory page allocation, we go through here, needing to peak inside
the current tasks cpuset to see if it has changed (it's 'mems_generation'
value doesn't match the last seen value we have stashed in the task
On Oct 4 2007 11:44, Pavel Machek wrote:
>diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
>index 7f1730f..1595a45 100644
>--- a/Documentation/CodingStyle
>+++ b/Documentation/CodingStyle
>@@ -71,6 +71,15 @@ used for indentation, and the above exam
>
> Get a decent editor and
Document sequence of keypresses that actually works. Yes, this changed
year-or-so ago.
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
index ef19142..10c8f69 100644
--- a/Documentation/sysrq.txt
+++ b/Documentation/sysrq.txt
@@
min_free_pages is critical for correctness, document it as such.
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
index a0ccc5b..e460c19 100644
--- a/Documentation/sysctl/vm.txt
+++ b/Documentation/sysctl/vm.txt
@@ -111,6 +111,12 @@ of kilobytes free. The VM uses this num
value for each lowmem
This cleans up kdump documentation a bit. Plus I do not think we want
to mention Linux trademark in _every_ file in documentation
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
index 2fedc08..faf0e27 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -13,7
Mention whitespace and bitfields style, prefer (!foo) to (foo == NULL)
in examples.
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 7f1730f..1595a45 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@
Hi Andrew,
On Thu, 4 Oct 2007 01:48:28 -0700, Andrew Morton wrote:
> 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
On Thu, Oct 04 2007, Pierre Ossman wrote:
> 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)
> >
>
"David J. Wilder" <[EMAIL PROTECTED]> writes:
> @@ -0,0 +1,160 @@
> +Trace Setup and Control
> +===
> +In the kernel, the trace interface provides a simple mechanism for
> +starting and managing data channels (traces) to user space.
Wasn't relayfs supposed to do that already?
On Tue, 2007-10-02 at 23:36 +0800, Robin Getz wrote:
> On Tue 2 Oct 2007 07:30, Kalle Pokki pondered:
> > 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
From: Patrick Caulfield <[EMAIL PROTECTED]>
If the castaddr passed to the userland API is NULL then don't overwrite the
existing castparam. This allows a different thread to cancel a lock request and
the CANCEL AST gets delivered to the original thread.
bz#306391 (for RHEL4) refers.
From: David Teigland <[EMAIL PROTECTED]>
Introduce a per-lockspace rwsem that's held in read mode by dlm_recv
threads while working in the dlm. This allows dlm_recv activity to be
suspended when the lockspace transitions to, from and between recovery
cycles.
The specific bug prompting this
From: Steven Whitehouse <[EMAIL PROTECTED]>
Signed-off-by: Steven Whitehouse <[EMAIL PROTECTED]>
diff --git a/fs/gfs2/ops_address.c b/fs/gfs2/ops_address.c
index 4002f41..873a511 100644
--- a/fs/gfs2/ops_address.c
+++ b/fs/gfs2/ops_address.c
@@ -747,7 +747,7 @@ int gfs2_releasepage(struct page
From: Steven Whitehouse <[EMAIL PROTECTED]>
The mapping may be NULL by the time the I/O has completed, so
we now get the superblock by a different route (via the bd and glock)
to avoid this problem.
Signed-off-by: Steven Whitehouse <[EMAIL PROTECTED]>
Cc: Wendy Cheng <[EMAIL PROTECTED]>
diff
From: Benjamin Marzinski <[EMAIL PROTECTED]>
There is a possible deadlock between two processes on the same node, where one
process is deleting an inode, and another process is looking for allocated but
unused inodes to delete in order to create more space.
process A does an iput() on inode X,
From: Wendy Cheng <[EMAIL PROTECTED]>
* GFS2 has been using i_cache array to store its indirect meta blocks.
Its flush routine doesn't correctly clean up all the entries. The
problem would show while multiple nodes do simultaneous writes to the
same file. Upon glock exclusive lock transfer, if
From: Bob Peterson <[EMAIL PROTECTED]>
The problem boiled down to a race between the gdlm_init_threads()
function initializing thread1 and its setting of blist = 1.
Essentially, "if (current == ls->thread1)" was checked by the thread
before the thread creator set ls->thread1.
Since thread1 is
From: Steven Whitehouse <[EMAIL PROTECTED]>
This patch cleans up the code for writing journaled data into the log.
It also removes the need to allocate a small "tag" structure for each
block written into the log. Instead we just keep count of the outstanding
I/O so that we can be sure that its
From: Patrick Caulfield <[EMAIL PROTECTED]>
Under high recovery loads dlm_sendd can monopolise the CPU and cause soft
lockups.
This one extra and one moved cond_resched() make it yield a little more during
such times keeping work moving.
Signed-Off-By: Patrick Caulfield <[EMAIL PROTECTED]>
From: Wendy Cheng <[EMAIL PROTECTED]>
Move inode deletion code out of blocking_cb handle_callback route to
avoid racy conditions that end up blocking lock_dlm1 thread. Fix
bugzilla 286821.
Signed-off-by: Wendy Cheng <[EMAIL PROTECTED]>
Signed-off-by: Steven Whitehouse <[EMAIL PROTECTED]>
diff
From: Abhijith Das <[EMAIL PROTECTED]>
This patch adds a new flag to the gfs2_holder structure GL_FLOCK.
It is set on holders of glocks representing flocks. This flag is
checked in add_to_queue() and a process is permitted to queue more
than one holder onto a glock if it is set. This solves the
From: Steven Whitehouse <[EMAIL PROTECTED]>
The following alters gfs2_trans_add_revoke() to take a struct
gfs2_bufdata as an argument. This eliminates the memory allocation which
was previously required by making use of the already existing struct
gfs2_bufdata. It makes some sanity checks to
From: Steven Whitehouse <[EMAIL PROTECTED]>
The old revoke structure was allocated using kalloc/kfree but
there is a slab cache for gfs2_bufdata, so we should use that
now that the structures have been converted.
This is part two of the patch series to merge the revoke
and gfs2_bufdata
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
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.
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]>
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
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
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: 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
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
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]>
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.
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: 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
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: 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]>
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: 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: 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: 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: 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: 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
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
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 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: 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
---
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
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:
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
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
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:
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,
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)
>> {
>>
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
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
301 - 400 of 902 matches
Mail list logo
