This time we have mostly clean ups. There is a bug fix for a NULL dereference
relating to ACLs, and another which improves (but does not fix entirely) an
allocation fall-back code path. The other three patches are small clean ups.
Steve.
Hi,
In contrast to recent merge windows, there are a number of interesting features
this time. There is a set of patches to improve performance in relation to
block reservations. Some correctness fixes for fallocate, and an update
to the freeze/thaw code which greatly simplyfies this code path.
Hi,
Not a huge amount this time... just four patches. This time we have a couple
of bug fixes, one relating to bad i_goal values which are now ignored (i_goal
is basically a hint so it is safe to so this) and another relating to the
saving of the dirent location during rename. There is one
Hi,
Here are a number of small fixes for GFS2. There is a fix for FIEMAP
on large sparse files, a negative dentry hashing fix, a fix for
flock, and a bug fix relating to d_splice_alias usage. There are
also (patches 1 and 5) a couple of updates which are less
critical, but small and low risk.
Hi,
This must be about the smallest merge window patch set ever for GFS2.
It is probably also the first one without a single patch from me. That
is down to a combination of factors, and I have some things in the works
that are not quite ready yet, that I hope to put in next time around.
Hi,
Here is a set of small fixes for GFS2. There is a fix to drop
s_umount which is copied in from the core vfs, two patches
relate to a hard to hit use after free and memory leak.
Two patches related to using DIO and buffered I/O on the same
file to ensure correct operation in relation to glock
Hi,
Here are a couple of very small, but important, fixes,
Steve.
Hi,
I'm just back from firstly Edinburgh, and secondly holiday, and the
merge window is again upon us. I've added in the three pending patches
which were under test while I was away and then that should be it for
this time.
The main feature of interest this time is quota updates. There are
some
Hi,
This is the smallest merge window patch set for GFS2 for quite
some time. Only one of the patches (moving gfs2_sync_meta) is
a non-bug fix patch, although the merge ordered and writeback
writepage patch is also a nice clean up.
A couple of the patches are quite recently added, due to my only
Hi,
Out of these fives patches, the one for ensuring that the number of
revokes is not exceeded, and the one for checking the glock is not
already held in gfs2_getxattr are the two most important. The latter
can be triggered by selinux.
The other three patches are very small and fix mostly
Hi,
There are a few bug fixes for various, mostly very minor corner
cases, plus some interesting new features. The new features
include atomic_open whose main benefit will be the reduction in
locking overhead in case of combined lookup/create and open operations,
sorting the log buffer lists by
There are four patches this time. The first fixes a problem where the
wrong descriptor type was being written into the log for journaled data
blocks. The second fixes a race relating to the deallocation of allocator
data. The third provides a fallback if kmalloc is unable to satisfy a
request to
This time there are just four fixes. There are a couple of minor updates
to the quota code, a fix for KConfig to ensure that only valid combinations
including GFS2 can be built, and a fix for a typo affecting end i/o
processing when writing the journal.
Also, there is a temporary fix for a
Hi,
Since the merge window is coming up soon, I'm posting the content of
the GFS2 -nmw tree as usual. There is not a whole lot of change this
time - there are some further changes which are in the works, but those
will be held over until next time.
Here there are some clean ups to inode
Hi,
Here are a few GFS2 fixes which are pending. There are two patches
which fix up a couple of minor issues in the DLM interface code,
a missing error path in gfs2_rs_alloc(), two patches which fix problems
during withdraw and a fix for discards/FITRIM when using 4k sector
sized devices,
Steve.
Hi,
Here are four small bug fixes for GFS2. There is no common theme here
really, just a few items that were fixed recently. The first fixes
lock name generation when the glock number is 0. The second fixes a
race allocating reservation structures and the final two fix a performance
issue by
Hi,
Here are a number of GFS2 bug fixes. There are three from Andy Price
which fix various issues spotted by automated code analysis. There are two
from Lukas Czerner fixing my mistaken assumptions as to how FITRIM
should work. Finally Ben Marzinski has fixed a bug relating to mmap and
atime and
Hi,
We've collected up a goodly number of patches in the -nmw tree now
and we can hold off any further changes until the following merge
window, so here is the current tree content.
The major feature this time is the rbm conversion in the resource
group code. The new struct gfs2_rbm specifies
Hi,
Here are three GFS2 fixes for the current kernel tree. These are all
related to the block reservation code which was added at the merge
window. That code will be getting an update at the forthcoming merge
window too. In the mean time though there are a few smaller issues
which should be
Hi,
As usual, here is the content of the GFS2 tree prior to sending
a merge request. Not a huge number of patches this time, but some
interesting features nonetheless.
A number of the earlier patches are aimed at cleaning up the resource
group code for the later patch which implements block
Hi,
Since the merge window appears to be fast approaching, here are the
current GFS2 patches. This time there are two main themes, one is
updates to the log code, mostly on the writing side. The other is
preparation for some block reservation work which will probably
land in the subsequent merge
Hi,
Here are four fixes for issues that have come up since the last
merge window,
Steve.
Hi,
On Mon, 2012-04-02 at 08:35 -0700, Randy Dunlap wrote:
On 03/26/2012 03:44 AM, Steven Whitehouse wrote:
Hi,
On Fri, 2012-03-23 at 18:06 -0400, Benjamin Poirier wrote:
[snip]
Instead of trying to select everything in GFS2, how about doing it this
way?
[PATCH] gfs2: use
Hi,
On Fri, 2012-03-23 at 18:06 -0400, Benjamin Poirier wrote:
[snip]
Instead of trying to select everything in GFS2, how about doing it this way?
[PATCH] gfs2: use depends instead of select in kconfig
Avoids having to duplicate the dependencies of what is 'select'ed (and on
down...)
on i386:
ERROR: sctp_do_peeloff [fs/dlm/dlm.ko] undefined!
GFS2_FS selects DLM (if GFS2_FS_LOCKING_DLM, which is enabled).
GFS2_FS selects IP_SCTP if DLM_SCTP, which is not enabled and not
used anywhere else in the kernel tree AFAICT.
DLM just always selects IP_SCTP.
Here's what we have
From: David Teigland teigl...@redhat.com
Date: Fri, 23 Mar 2012 15:41:52 -0400
Why does gfs2 Kconfig bother with SCTP at all? It seems that line should
just be removed. I'll also remove EXPERIMENTAL. I don't understand the
vagaries of Kconfig, so a dumb question, how could sctp_do_peeloff
Hi,
On Fri, 2012-03-23 at 13:06 -0700, Randy Dunlap wrote:
On 03/23/2012 12:41 PM, David Teigland wrote:
on i386:
ERROR: sctp_do_peeloff [fs/dlm/dlm.ko] undefined!
GFS2_FS selects DLM (if GFS2_FS_LOCKING_DLM, which is enabled).
GFS2_FS selects IP_SCTP if DLM_SCTP, which is not
On Fri, Mar 23, 2012 at 01:06:05PM -0700, Randy Dunlap wrote:
GFS2_FS selects DLM (if GFS2_FS_LOCKING_DLM, which is enabled).
GFS2_FS selects IP_SCTP if DLM_SCTP, which is not enabled and not
used anywhere else in the kernel tree AFAICT.
DLM just always selects IP_SCTP.
Here's what we
Hi,
On Mon, 2012-03-19 at 08:18 -0700, Randy Dunlap wrote:
On 03/19/2012 07:59 AM, Steven Whitehouse wrote:
Hi,
On Mon, 2012-03-19 at 07:45 -0700, Randy Dunlap wrote:
On 03/19/2012 03:25 AM, Steven Whitehouse wrote:
Hi,
Not a huge number of patches this time. Some notable new
Hi,
Not a huge number of patches this time. Some notable new features
though:
- Glock stats gathering (v. useful for performance analysis)
- FITRIM ioctl support
- Sorting the ordered write list (big performance increase when the workload
doesn't result in the write requests being nicely
Hi,
On Mon, 2012-03-19 at 07:45 -0700, Randy Dunlap wrote:
On 03/19/2012 03:25 AM, Steven Whitehouse wrote:
Hi,
Not a huge number of patches this time. Some notable new features
though:
- Glock stats gathering (v. useful for performance analysis)
- FITRIM ioctl support
-
Hi,
On Mon, 2012-03-19 at 08:18 -0700, Randy Dunlap wrote:
On 03/19/2012 07:59 AM, Steven Whitehouse wrote:
Hi,
On Mon, 2012-03-19 at 07:45 -0700, Randy Dunlap wrote:
On 03/19/2012 03:25 AM, Steven Whitehouse wrote:
Hi,
Not a huge number of patches this time. Some notable new
Hi,
Here are four patches which provided fixes for bugs found in the
current upstream code. Please see individual patches for
descriptions,
Steve.
Hi,
The following patch set contains one large patch which was previously
in the DLM tree (and hence also in linux-next) but which is entirely
focused on GFS2, and has thus been moved into the GFS2 tree after
the merge of the recent DLM patches. In addition there are a few small
bug fixes too,
Hi,
The main feature this time is clean up around the allocation and
resource group code. Otherwise the remainder is mostly small
bug fixes.
I've held back the glock stats patch and that will probably be
ready for the following merge window with a bit of luck,
Steve.
Hi,
Not a lot new this time... the addition of a cache for the directory hash table
improve directory read/lookup speed, automatic adjustment of the glock hold
time improves performance for some contention corner cases. S_NOSEC support
is another performance related change, plus a nice clean up
Hi,
The following three fixes should help ensure that 3.0 is the best
release yet, GFS2-wise at least. I've had the first two queued for
some time waiting for the final one of this set. All three are relatively
short, although the third is a bit longer than the others, mainly
due to the extra
Hi,
Here are a couple of small fixes which just missed the previous pull
request. Both fairly short and self-explanatory,
Steve.
Hi,
This time, most of the GFS2 patches are code clean up, although there
are a few bug fixes (fallocate/ail writeback/end of life inodes/nlink) and
some new features (new tracepoint tracing flags, using the UUID field
in the generic superblock).
The changes can be broadly divided into three
Hi,
Here are four fixes for GFS2. See the individual patches for the detailed
descriptions,
Steve.
Hi,
The most interesting feature in this patch set is the RCU glock
patch which has been a long time coming, but is finally here. That
patch contains most of the changes this time. The other patches ins
this set are mostly smaller bug fixes and performance improvements.
Steve.
Hi,
This is a bit early this time, but I'm not expecting to add any more
features to this patch set before the merge window. In fact it is
mostly clean up and fixes anyway. So I'm pushing it out now to let
everybody see it ahead of time.
The only user visible new feature this time is the
Hi,
I know the merge window isn't open yet, but at this stage I'm going to
hold off on any larger patches until the following merge window so this
patch set isn't likely to change much, hence kicking it out a bit early
for review.
There are a few interesting points to note in this patch set:
o
Hi,
Here are a few small fixes for GFS2,
Steve.
Hi,
These are three important, but relatively small, bug fixes for GFS2.
The first prevents a kernel BUG triggering in a relatively unlikely
(but possible) scenario when a log flush caused by glock demotion
races with a log flush from some other initiator (e.g. fsync).
The second and third
Hi,
Nothing very exciting this time mostly minor bug fixes and
a docs update. The gfs2_logd patch has been hanging around for
a long time and is now finally integrated. It is the first step
towards a longer term goal of improving performance in that
area,
Steve.
Here are three small (but important!) fixes to GFS2.
Steve.
Hi,
Here are a couple of GFS2 fixes. Both are one-liners,
Steve.
Hi,
Here are a couple of patches which between them fix a problem where
occasionally it was possible for the GFS2 module to be unloaded
before all the glocks were deallocated, which, needless to say, made
the slab allocator unhappy,
Steve.
Here are four small fixes for GFS2. Assuming that nobody spots
any errors, I'll be sending a pull request for these shortly,
Steve.
As merge time is approaching, here is the current content of the
GFS2 -nmw git tree. I'm not expecting to take any more patches
now for the current merge window unless any last minute bugs
are discovered.
There is not a huge amount new this time. Some extra context for
uevent messages, better
Hi,
Here is the current content of the GFS2 -fixes git tree. Nothing
very exciting this time... some fixes for issues we've
had relating to flushing glocks/memory usage, plus a couple of
other fixes relating to statfs and the timely removal of inodes
which have been unlinked on a remote node,
In preparation for the next merge window, here is the current content
of the GFS2 git tree. Firstly, we have one new feature, which is
support for the FIEMAP ioctl. That patch does touch some code
outside of GFS2 itself, but its the only patch in this series which
does so.
The remaining patches
I'm guessing that the merge window opening might not be too far
away now, and in any case, I won't have quite my normal internet
access next week. So I'm pushing out the current GFS2 tree so
that (I hope) there will be time to fix any issues.
Again, there are fewer patches here. A lot of them are
So, although the merge window isn't yet open, I'm guessing that its
probably not too far away, hence this posting of the contents of
the current GFS2 -nmw git tree.
This time the big news is locking changes, although having said that,
there are far fewer queued patches in total than I've had for
Hi,
Here is a set of three patches which constitute the current set of
fixes for GFS2. They are all fairly minor changes, but useful
nonetheless,
Steve.
This is the current content of the GFS2 -nmw git tree. Mostly bug
fixes, there are some changes relating to block mapping which are
working towards cleaning up this code and allowing more efficient
block mapping. There is a second part to that work which is not
included in this patch set - the
Hi,
Here is the current GFS2 patch queue. You'll notice that this time
there are no DLM patches in this list. That is because the DLM team
are setting up their own git tree and this future DLM patches will
be sent directly by them rather than via the GFS2 tree.
Most of this set of patches is
58 matches
Mail list logo
