On 06/18/2014 07:23 PM, Joseph Salisbury wrote:
BugLink: http://bugs.launchpad.net/bugs/1324953
Hello,
Please consider including upstream commit c41570c9 in the next v3.13.y
release. It was included upstream as of v3.14-rc2. It has been tested and
confirmed to resolve
Make sure compiler won't do weird things with limits. E.g. fetching
them twice may return 2 different values after writable limits are
implemented.
I.e. either use rlimit helpers added in
3e10e716abf3c71bdb5d86b8f507f9e72236c9cd
or ACCESS_ONCE if not applicable.
Signed-off-by: Jiri Slaby jsl
On 02/10/2010 09:01 PM, Chris Mason wrote:
Thanks, I have this queued up for .34
Hi, this is still not merged. Was it lost?
On Wed, Feb 10, 2010 at 09:00:09PM +0100, Jiri Slaby wrote:
Make sure compiler won't do weird things with limits. E.g. fetching
them twice may return 2 different values
On 09/02/2010 03:02 AM, David Rientjes wrote:
--- a/include/linux/slab.h
+++ b/include/linux/slab.h
@@ -334,6 +334,57 @@ static inline void *kzalloc_node(size_t size, gfp_t
flags, int node)
return kmalloc_node(size, flags | __GFP_ZERO, node);
}
+/**
+ * kmalloc_nofail -
Make sure compiler won't do weird things with limits. E.g. fetching
them twice may return 2 different values after writable limits are
implemented.
I.e. either use rlimit helpers added in
3e10e716abf3c71bdb5d86b8f507f9e72236c9cd
or ACCESS_ONCE if not applicable.
Signed-off-by: Jiri Slaby jsl
Make sure compiler won't do weird things with limits. E.g. fetching
them twice may return 2 different values after writable limits are
implemented.
I.e. either use rlimit helpers added in
3e10e716abf3c71bdb5d86b8f507f9e72236c9cd
or ACCESS_ONCE if not applicable.
Signed-off-by: Jiri Slaby jsl
Make sure compiler won't do weird things with limits. E.g. fetching
them twice may return 2 different values after writable limits are
implemented.
I.e. either use rlimit helpers added in
3e10e716abf3c71bdb5d86b8f507f9e72236c9cd
or ACCESS_ONCE if not applicable.
Signed-off-by: Jiri Slaby jsl
Stanse found 2 memory leaks in relocate_block_group and
__btrfs_map_block. cluster and multi are not freed/assigned on all
paths. Fix that.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Chris Mason chris.ma...@oracle.com
Cc: linux-btrfs@vger.kernel.org
---
fs/btrfs/relocation.c |4 +++-
fs
Hi,
Stanse found unreachable code in btrfs_insert_some_items below (don't
look at the line numbers, they are on preprocessed code). I would fix
that if I knew how.
Should the assignment be after the if, before the break or nowhere?
3068|int btrfs_insert_some_items(struct btrfs_trans_handle
worker memory is already freed on one fail path in btrfs_start_workers,
but is still dereferenced. Switch the dereference and kfree.
Signed-off-by: Jiri Slaby jirisl...@gmail.com
---
fs/btrfs/async-thread.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/btrfs/async
10 matches
Mail list logo
