On Fri, 2007-12-28 at 12:33 +0100, Peter Zijlstra wrote:
On Fri, 2007-12-28 at 16:03 +0800, Fengguang Wu wrote:
Andrew,
This patch fixed the 'pdflush stuck in D state' bug
http://bugzilla.kernel.org/show_bug.cgi?id=9291
and should be pushed to mainline ASAP.
---
When
On Fri, 2007-12-28 at 10:25 -0600, Dave Kleikamp wrote:
On Fri, 2007-12-28 at 12:33 +0100, Peter Zijlstra wrote:
I'm not liking this open-coded tag_clear, although I currently fail to
come up with a nice solution.
I'm looking at __block_write_full_page() for guidance. The situation
On Sat, 2007-12-29 at 10:21 +0800, Fengguang Wu wrote:
On Fri, Dec 28, 2007 at 10:53:14AM -0600, Dave Kleikamp wrote:
---
diff -Nurp linux-2.6.24-rc6-git5/fs/jfs/jfs_metapage.c
linux/fs/jfs/jfs_metapage.c
--- linux-2.6.24-rc6-git5/fs/jfs/jfs_metapage.c 2007-12-28
10:28
On Wed, 2007-12-12 at 15:57 +1100, Nick Piggin wrote:
> On Tuesday 11 December 2007 08:30, Dave Kleikamp wrote:
> > Nick,
> > I've played with the fast_gup patch a bit. I was able to find a problem
> > in follow_hugetlb_page() that Adam Litke fixed. I'm haven't
On Wed, 2007-12-12 at 15:57 +1100, Nick Piggin wrote:
On Tuesday 11 December 2007 08:30, Dave Kleikamp wrote:
Nick,
I've played with the fast_gup patch a bit. I was able to find a problem
in follow_hugetlb_page() that Adam Litke fixed. I'm haven't been brave
enough to implement
On Mon, 2007-10-15 at 22:25 +1000, Nick Piggin wrote:
> On Monday 15 October 2007 04:19, Siddha, Suresh B wrote:
> > On Sun, Oct 14, 2007 at 11:01:02AM +1000, Nick Piggin wrote:
> > > This is just a really quick hack, untested ATM, but one that
> > > has at least a chance of working (on x86).
>
On Mon, 2007-10-15 at 22:25 +1000, Nick Piggin wrote:
On Monday 15 October 2007 04:19, Siddha, Suresh B wrote:
On Sun, Oct 14, 2007 at 11:01:02AM +1000, Nick Piggin wrote:
This is just a really quick hack, untested ATM, but one that
has at least a chance of working (on x86).
When we
On Tue, 2007-11-13 at 18:05 -0800, Joe Perches wrote:
> Remove defconfig ptr comparison to 0
>
> Remove sparse warning: Using plain integer as NULL pointer
>
> Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]>
I've add
On Tue, 2007-11-13 at 18:05 -0800, Joe Perches wrote:
Remove defconfig ptr comparison to 0
Remove sparse warning: Using plain integer as NULL pointer
Signed-off-by: Joe Perches [EMAIL PROTECTED]
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED]
I've added this to the jfs git tree.
Thanks
Memory barriers aren't one of my strengths, but this appears correct.
Acked-by: Dave Kleikamp <[EMAIL PROTECTED]>
On Fri, 2007-10-26 at 12:09 +1000, Nick Piggin wrote:
> Index: linux-2.6/fs/jfs/jfs_metapage.c
> ===
>
Memory barriers aren't one of my strengths, but this appears correct.
Acked-by: Dave Kleikamp [EMAIL PROTECTED]
On Fri, 2007-10-26 at 12:09 +1000, Nick Piggin wrote:
Index: linux-2.6/fs/jfs/jfs_metapage.c
===
--- linux-2.6.orig
On Fri, 2007-10-19 at 22:34 -0700, Andrew Morton wrote:
> On Sat, 20 Oct 2007 13:57:54 +0900 Mattia Dongili <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Oct 11, 2007 at 09:31:26PM -0700, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/
On Fri, 2007-10-19 at 22:34 -0700, Andrew Morton wrote:
On Sat, 20 Oct 2007 13:57:54 +0900 Mattia Dongili [EMAIL PROTECTED] wrote:
On Thu, Oct 11, 2007 at 09:31:26PM -0700, Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/
Hey
On Sat, 2007-10-13 at 12:28 -0700, Randy Dunlap wrote:
> On Sat, 13 Oct 2007 15:11:10 -0400 Jeff Garzik wrote:
>
> >
> > From: Dave Kleikamp <[EMAIL PROTECTED]>
> >
> > commit 6712ecf8f648118c3363c142196418f89a510b90 removed some "return 0;"
>
[ 9159.490780] Rebooting in 30 seconds..
I don't have time to test this now, but the bio_endio patches ended up
removing some return statements that need to stay. I think this should
fix it.
JFS: Bio cleanup: Replace missing return statements
commit 6712ecf8f648118c3363c142196418f89a510b90 remo
this should
fix it.
JFS: Bio cleanup: Replace missing return statements
commit 6712ecf8f648118c3363c142196418f89a510b90 removed some return 0;
statements, rather than changing them to null returns.
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED]
diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
On Sat, 2007-10-13 at 12:28 -0700, Randy Dunlap wrote:
On Sat, 13 Oct 2007 15:11:10 -0400 Jeff Garzik wrote:
From: Dave Kleikamp [EMAIL PROTECTED]
commit 6712ecf8f648118c3363c142196418f89a510b90 removed some return 0;
statements, rather than changing them to null returns.
Is my
I'd say add my ack, but I see it's already been picked up.
Thanks,
Shaggy
On Fri, 2007-10-12 at 00:01 -0400, Jeff Garzik wrote:
> Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
>
> diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
> index 57c3b8a..ccfd029 100644
> --- a/fs/jfs/jfs_logmgr.c
I'd say add my ack, but I see it's already been picked up.
Thanks,
Shaggy
On Fri, 2007-10-12 at 00:01 -0400, Jeff Garzik wrote:
Signed-off-by: Jeff Garzik [EMAIL PROTECTED]
diff --git a/fs/jfs/jfs_logmgr.c b/fs/jfs/jfs_logmgr.c
index 57c3b8a..ccfd029 100644
--- a/fs/jfs/jfs_logmgr.c
+++
On Tue, 2007-10-02 at 14:24 +0100, David Howells wrote:
> Dave Kleikamp <[EMAIL PROTECTED]> wrote:
>
> > Of course, the cast is unnecessary,
>
> The cast is necessary as the argument is a const pointer and the return type
> is not.
Ah yes. I stand corrected.
-
On Tue, 2007-10-02 at 13:32 +0100, David Howells wrote:
> Zach Brown <[EMAIL PROTECTED]> wrote:
>
> > /* haha, continuing the fine tradition of terrible names in this api.. */
> > static inline void *PTR_PTR(void *err_ptr) {
> > BUG_ON(!IS_ERR(err_ptr) || !err_ptr);
> > return err_ptr;
On Tue, 2007-10-02 at 13:32 +0100, David Howells wrote:
Zach Brown [EMAIL PROTECTED] wrote:
/* haha, continuing the fine tradition of terrible names in this api.. */
static inline void *PTR_PTR(void *err_ptr) {
BUG_ON(!IS_ERR(err_ptr) || !err_ptr);
return err_ptr;
}
How
On Tue, 2007-10-02 at 14:24 +0100, David Howells wrote:
Dave Kleikamp [EMAIL PROTECTED] wrote:
Of course, the cast is unnecessary,
The cast is necessary as the argument is a const pointer and the return type
is not.
Ah yes. I stand corrected.
--
David Kleikamp
IBM Linux Technology
of an inode in the event of an error.
>
> jfs_fill_super() returns any error incurred when getting the root inode
> instead of EINVAL.
>
> Signed-off-by: David Howells <[EMAIL PROTECTED]>
Acked-by: Dave Kleikamp <[EMAIL PROTECTED]>
> ---
>
> fs/jfs/i
in the event of an error.
jfs_fill_super() returns any error incurred when getting the root inode
instead of EINVAL.
Signed-off-by: David Howells [EMAIL PROTECTED]
Acked-by: Dave Kleikamp [EMAIL PROTECTED]
---
fs/jfs/inode.c | 20
fs/jfs/jfs_inode.h |2 +-
fs
On Wed, 2007-09-19 at 14:26 -0500, Dave Kleikamp wrote:
> On Wed, 2007-09-19 at 12:15 -0700, Mingming Cao wrote:
>
> > Here is the patch to clean up __GFP_NOFAIL flag in jbd/jbd2. In all
> > cases except one handles memory allocation failure so I get rid of those
&g
On Wed, 2007-09-19 at 12:15 -0700, Mingming Cao wrote:
> Here is the patch to clean up __GFP_NOFAIL flag in jbd/jbd2. In all
> cases except one handles memory allocation failure so I get rid of those
> GFP_NOFAIL flags.
>
> Also, shouldn't we use GFP_KERNEL instead of GFP_NOFS flag for kmalloc
>
On Wed, 2007-09-19 at 13:44 +0200, Oliver Neukum wrote:
> Am Donnerstag 13 September 2007 schrieb Dave Kleikamp:
> > On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
> >
> > > Subject : umount triggers a warning in jfs and takes almost a
>
On Wed, 2007-09-19 at 13:44 +0200, Oliver Neukum wrote:
Am Donnerstag 13 September 2007 schrieb Dave Kleikamp:
On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
Subject : umount triggers a warning in jfs and takes almost a
minute
References : http://lkml.org
On Wed, 2007-09-19 at 12:15 -0700, Mingming Cao wrote:
Here is the patch to clean up __GFP_NOFAIL flag in jbd/jbd2. In all
cases except one handles memory allocation failure so I get rid of those
GFP_NOFAIL flags.
Also, shouldn't we use GFP_KERNEL instead of GFP_NOFS flag for kmalloc
in
On Wed, 2007-09-19 at 14:26 -0500, Dave Kleikamp wrote:
On Wed, 2007-09-19 at 12:15 -0700, Mingming Cao wrote:
Here is the patch to clean up __GFP_NOFAIL flag in jbd/jbd2. In all
cases except one handles memory allocation failure so I get rid of those
GFP_NOFAIL flags.
Also
On Tue, 2007-09-18 at 09:35 -0700, Mingming Cao wrote:
> On Tue, 2007-09-18 at 10:04 +0100, Christoph Hellwig wrote:
> > On Mon, Sep 17, 2007 at 03:57:31PM -0700, Mingming Cao wrote:
> > > Here is the incremental small cleanup patch.
> > >
> > > Remove kamlloc usages in jbd/jbd2 and consistently
On Tue, 2007-09-18 at 16:24 +0200, Jan Kara wrote:
> > Subject : umount triggers a warning in jfs and takes almost a minute
> > References : http://lkml.org/lkml/2007/9/4/73
> > Last known good : ?
> > Submitter : Oliver Neukum <[EMAIL PROTECTED]>
> > Caused-By : ?
> >
On Tue, 2007-09-18 at 16:24 +0200, Jan Kara wrote:
Subject : umount triggers a warning in jfs and takes almost a minute
References : http://lkml.org/lkml/2007/9/4/73
Last known good : ?
Submitter : Oliver Neukum [EMAIL PROTECTED]
Caused-By : ?
Handled-By
On Tue, 2007-09-18 at 09:35 -0700, Mingming Cao wrote:
On Tue, 2007-09-18 at 10:04 +0100, Christoph Hellwig wrote:
On Mon, Sep 17, 2007 at 03:57:31PM -0700, Mingming Cao wrote:
Here is the incremental small cleanup patch.
Remove kamlloc usages in jbd/jbd2 and consistently use
On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
> Subject : umount triggers a warning in jfs and takes almost a minute
> References : http://lkml.org/lkml/2007/9/4/73
> Last known good : ?
> Submitter : Oliver Neukum <[EMAIL PROTECTED]>
> Caused-By : ?
>
On Wed, 2007-09-12 at 18:58 +0200, Michal Piotrowski wrote:
Subject : umount triggers a warning in jfs and takes almost a minute
References : http://lkml.org/lkml/2007/9/4/73
Last known good : ?
Submitter : Oliver Neukum [EMAIL PROTECTED]
Caused-By : ?
Handled-By
On Sat, 2007-09-08 at 13:11 +0200, Michal Piotrowski wrote:
> Hi all,
>
> Here is a list of some known regressions in 2.6.23-rc5.
>
> Feel free to add new regressions/remove fixed etc.
> http://kernelnewbies.org/known_regressions
> FS
>
> Subject : umount triggers a warning in jfs and
On Sat, 2007-09-08 at 13:11 +0200, Michal Piotrowski wrote:
Hi all,
Here is a list of some known regressions in 2.6.23-rc5.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
FS
Subject : umount triggers a warning in jfs and takes
On Tue, 2007-08-28 at 07:11 +0800, Michael Deegan wrote:
> Hi,
>
> On Tue Aug 7 16:00:19 GMT 2007, Martin Koegler wrote:
> > A vanilla 2.6.22 kernel (SMP PREEMPT i686) produced the following messages,
> > while working with a CIFS mount point:
> >
> > Aug 7 16:12:30 localhost kernel: BUG:
On Tue, 2007-08-28 at 07:11 +0800, Michael Deegan wrote:
Hi,
On Tue Aug 7 16:00:19 GMT 2007, Martin Koegler wrote:
A vanilla 2.6.22 kernel (SMP PREEMPT i686) produced the following messages,
while working with a CIFS mount point:
Aug 7 16:12:30 localhost kernel: BUG: scheduling
Thanks, but Jack Stone submitted the same patch a few weeks ago. It's
already in the jfs git tree and the -mm kernel.
Shaggy
On Fri, 2007-08-24 at 02:36 +0200, Jesper Juhl wrote:
> There's no need to cast the, void *, return value of kmalloc() when
> assigning to a pointer variable.
>
>
Thanks, but Jack Stone submitted the same patch a few weeks ago. It's
already in the jfs git tree and the -mm kernel.
Shaggy
On Fri, 2007-08-24 at 02:36 +0200, Jesper Juhl wrote:
There's no need to cast the, void *, return value of kmalloc() when
assigning to a pointer variable.
ttr inode op.
Here's my ack for the jfs piece.
>
> Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
Acked-by: Dave Kleikamp <[EMAIL PROTECTED]>
--
David Kleikamp
IBM Linux Technology Center
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
.
Here's my ack for the jfs piece.
Signed-off-by: Jeff Layton [EMAIL PROTECTED]
Acked-by: Dave Kleikamp [EMAIL PROTECTED]
--
David Kleikamp
IBM Linux Technology Center
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
On Mon, 2007-08-06 at 09:54 -0400, Jeff Layton wrote:
> Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
Acked-by: Dave Kleikamp <[EMAIL PROTECTED]>
> ---
> fs/jfs/acl.c |2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/fs/jfs/acl.c
On Mon, 2007-08-06 at 09:54 -0400, Jeff Layton wrote:
Signed-off-by: Jeff Layton [EMAIL PROTECTED]
Acked-by: Dave Kleikamp [EMAIL PROTECTED]
---
fs/jfs/acl.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/fs/jfs/acl.c b/fs/jfs/acl.c
index 4d84bdc..34ca314 100644
On Wed, 2007-08-01 at 15:33 -0400, Josef Sipek wrote:
> On Wed, Aug 01, 2007 at 02:10:31PM -0500, Dave Kleikamp wrote:
> > On Wed, 2007-08-01 at 14:44 -0400, Josef Sipek wrote:
> > > Now what? How do you rename? Do you rename in the same branch (assuming it
> &g
On Wed, 2007-08-01 at 14:44 -0400, Josef Sipek wrote:
> Alright not the greatest of examples, there is something to be said about
> symmetry, so...let me try again :)
>
> /a/
> /b/bar(whiteout for bar)
> /c/foo/qwerty
>
> Now, let's mount a union of {a,b,c}, and we'll see:
>
> $
On Tue, 2007-07-31 at 13:11 -0400, Josef Sipek wrote:
> On Tue, Jul 31, 2007 at 07:00:12PM +0200, Jan Blunck wrote:
> > On Tue, Jul 31, Josef Sipek wrote:
> >
> > > On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> > > > Introduce white-out support to ext2.
> > >
> > > I think
On Tue, 2007-07-31 at 13:11 -0400, Josef Sipek wrote:
On Tue, Jul 31, 2007 at 07:00:12PM +0200, Jan Blunck wrote:
On Tue, Jul 31, Josef Sipek wrote:
On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
Introduce white-out support to ext2.
I think storing whiteouts on the
On Wed, 2007-08-01 at 14:44 -0400, Josef Sipek wrote:
Alright not the greatest of examples, there is something to be said about
symmetry, so...let me try again :)
/a/
/b/bar(whiteout for bar)
/c/foo/qwerty
Now, let's mount a union of {a,b,c}, and we'll see:
$ find /u
On Wed, 2007-08-01 at 15:33 -0400, Josef Sipek wrote:
On Wed, Aug 01, 2007 at 02:10:31PM -0500, Dave Kleikamp wrote:
On Wed, 2007-08-01 at 14:44 -0400, Josef Sipek wrote:
Now what? How do you rename? Do you rename in the same branch (assuming it
is rw)?
Er, no. According
Looks good. I'll push it through the jfs git tree.
Thanks,
Shaggy
On Tue, 2007-07-31 at 13:53 +0100, [EMAIL PROTECTED] wrote:
> Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
>
> CC: David Kleikamp <[EMAIL PROTECTED]>
> ---
> fs/jfs/jfs_dtree.c |8 ++--
> 1 file changed, 2
Looks good. I'll push it through the jfs git tree.
Thanks,
Shaggy
On Tue, 2007-07-31 at 13:53 +0100, [EMAIL PROTECTED] wrote:
Signed-off-by: Jack Stone [EMAIL PROTECTED]
CC: David Kleikamp [EMAIL PROTECTED]
---
fs/jfs/jfs_dtree.c |8 ++--
1 file changed, 2 insertions(+), 6
On Mon, 2007-07-30 at 10:29 -0400, Justin Piszcz wrote:
> Overall JFS seems the fastest but reviewing the mailing list for JFS it
> seems like there a lot of problems, especially when people who use JFS > 1
> year, their speed goes to 5 MiB/s over time and the defragfs tool has been
>
On Mon, 2007-07-30 at 10:29 -0400, Justin Piszcz wrote:
Overall JFS seems the fastest but reviewing the mailing list for JFS it
seems like there a lot of problems, especially when people who use JFS 1
year, their speed goes to 5 MiB/s over time and the defragfs tool has been
removed(?)
On Fri, 2007-07-13 at 17:13 +1000, David Chinner wrote:
> On Thu, Jul 12, 2007 at 09:34:57AM -0700, Dave Hansen wrote:
> > On Thu, 2007-07-12 at 18:31 +0200, Andrea Arcangeli wrote:
> > > On Fri, Jul 13, 2007 at 12:44:49AM +1000, David Chinner wrote:
> > > > That's crap. Just because a machine has
On Fri, 2007-07-13 at 17:13 +1000, David Chinner wrote:
On Thu, Jul 12, 2007 at 09:34:57AM -0700, Dave Hansen wrote:
On Thu, 2007-07-12 at 18:31 +0200, Andrea Arcangeli wrote:
On Fri, Jul 13, 2007 at 12:44:49AM +1000, David Chinner wrote:
That's crap. Just because a machine has lots of
On Thu, 2007-07-12 at 12:38 +0100, Andy Whitcroft wrote:
> Andrew Morton wrote:
> >> + if (ext4_ext_check_header(inode, ext_block_hdr(bh),
> >> + depth - i - 1)) {
> >> + err = -EIO;
> >> +
On Thu, 2007-07-12 at 12:38 +0100, Andy Whitcroft wrote:
Andrew Morton wrote:
+ if (ext4_ext_check_header(inode, ext_block_hdr(bh),
+ depth - i - 1)) {
+ err = -EIO;
+
On Wed, 2007-07-11 at 15:05 +1000, Neil Brown wrote:
> It just occurred to me:
>
> If i_version is 64bit, then knfsd would need to be careful when
> reading it on a 32bit host. What are the locking rules?
How does knfsd use i_version? I would think that if all it was doing
was to compare
On Wed, 2007-07-11 at 15:05 +1000, Neil Brown wrote:
It just occurred to me:
If i_version is 64bit, then knfsd would need to be careful when
reading it on a 32bit host. What are the locking rules?
How does knfsd use i_version? I would think that if all it was doing
was to compare
(-)
through these ChangeSets:
Commit: 288e4d838d1e999c0515f85a337cacb2be233071
Author: Dave Kleikamp <[EMAIL PROTECTED]> Wed, 13 Jun 2007 10:17:50 -0500
JFS: Update print_hex_dump() syntax
Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]
(-)
through these ChangeSets:
Commit: 288e4d838d1e999c0515f85a337cacb2be233071
Author: Dave Kleikamp [EMAIL PROTECTED] Wed, 13 Jun 2007 10:17:50 -0500
JFS: Update print_hex_dump() syntax
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED]
Commit
On Thu, 2007-06-28 at 11:33 -0700, Andrew Morton wrote:
> On Thu, 28 Jun 2007 23:27:57 +0530 "Amit K. Arora" <[EMAIL PROTECTED]> wrote:
>
> > > Please drop the non-ext4 patches from the ext4 tree and send incremental
> > > patches against the (non-ext4) fallocate patches in -mm.
> >
> > Please
s'
drivers/md/dm-mod.o:drivers/md/dm-netlink.h:51: first defined here
make[2]: *** [drivers/md/built-in.o] Error 1
I was able to fix it by making the dummy inline functions static.
Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]>
diff -Nurp linux-2.6.22-rc6-mm1/drivers/md/dm-netlink.h
-netlink.h:51: first defined here
make[2]: *** [drivers/md/built-in.o] Error 1
I was able to fix it by making the dummy inline functions static.
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED]
diff -Nurp linux-2.6.22-rc6-mm1/drivers/md/dm-netlink.h
linux/drivers/md/dm-netlink.h
--- linux-2.6.22-rc6-mm1
On Thu, 2007-06-28 at 11:33 -0700, Andrew Morton wrote:
On Thu, 28 Jun 2007 23:27:57 +0530 Amit K. Arora [EMAIL PROTECTED] wrote:
Please drop the non-ext4 patches from the ext4 tree and send incremental
patches against the (non-ext4) fallocate patches in -mm.
Please let us know what
On Tue, 2007-06-26 at 13:32 -0700, Andrew Morton wrote:
> On Fri, 15 Jun 2007 00:15:55 +0200
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > nobh_{prepare,commit}_write() are no longer used.
>
> wth? What happened to ext2 and ext3 nobh mode? They seem to
> have magically and unchangeloggedly
On Tue, 2007-06-26 at 13:32 -0700, Andrew Morton wrote:
On Fri, 15 Jun 2007 00:15:55 +0200
Adrian Bunk [EMAIL PROTECTED] wrote:
nobh_{prepare,commit}_write() are no longer used.
wth? What happened to ext2 and ext3 nobh mode? They seem to
have magically and unchangeloggedly disappeared?
On Thu, 2007-06-14 at 15:04 -0700, Andrew Morton wrote:
> > On Thu, 14 Jun 2007 14:37:33 -0700 (PDT) Christoph Lameter <[EMAIL
> > PROTECTED]> wrote:
> > On Thu, 14 Jun 2007, Andrew Morton wrote:
> >
> > > We want the 100% case.
> >
> > Yes that is what we intend to do. Universal support for
On Thu, 2007-06-14 at 15:04 -0700, Andrew Morton wrote:
On Thu, 14 Jun 2007 14:37:33 -0700 (PDT) Christoph Lameter [EMAIL
PROTECTED] wrote:
On Thu, 14 Jun 2007, Andrew Morton wrote:
We want the 100% case.
Yes that is what we intend to do. Universal support for larger blocksize.
On Sat, 2007-06-02 at 09:28 -0700, Jeremy Fitzhardinge wrote:
> Dave Kleikamp wrote:
> > I'm on Christoph's side here. I don't think it makes sense for any code
> > to ask to allocate zero bytes of memory and expect valid memory to be
> > returned.
> >
On Sat, 2007-06-02 at 09:28 -0700, Jeremy Fitzhardinge wrote:
Dave Kleikamp wrote:
I'm on Christoph's side here. I don't think it makes sense for any code
to ask to allocate zero bytes of memory and expect valid memory to be
returned.
Yes, everyone agrees on that. If you do
On Fri, 2007-06-01 at 11:58 -0700, Jeremy Fitzhardinge wrote:
> Christoph Lameter wrote:
> > Hmmm... We got there because SLUB initially return NULL for kmalloc(0).
> > Rationale: The user did not request any memory so we wont give him
> > any.
> >
> > That (to my surprise) caused some strange
On Fri, 2007-06-01 at 11:58 -0700, Jeremy Fitzhardinge wrote:
Christoph Lameter wrote:
Hmmm... We got there because SLUB initially return NULL for kmalloc(0).
Rationale: The user did not request any memory so we wont give him
any.
That (to my surprise) caused some strange behavior of
On Thu, 2007-05-31 at 16:25 +0200, Jörn Engel wrote:
> --- linux-2.6.21logfs/fs/jfs/jfs_txnmgr.c~I_LOCK2007-05-07
> 10:28:55.0 +0200
> +++ linux-2.6.21logfs/fs/jfs/jfs_txnmgr.c 2007-05-29
> 13:10:32.0 +0200
> @@ -1286,7 +1286,14 @@ int txCommit(tid_t tid, /*
On Thu, 2007-05-31 at 16:25 +0200, Jörn Engel wrote:
--- linux-2.6.21logfs/fs/jfs/jfs_txnmgr.c~I_LOCK2007-05-07
10:28:55.0 +0200
+++ linux-2.6.21logfs/fs/jfs/jfs_txnmgr.c 2007-05-29
13:10:32.0 +0200
@@ -1286,7 +1286,14 @@ int txCommit(tid_t tid, /*
On Tue, 2007-05-29 at 13:14 -0500, Roger Heflin wrote:
> Dave Kleikamp wrote:
> > On Tue, 2007-05-29 at 12:16 -0500, Roger Heflin wrote:
> >
> >> Dave,
> >>
> >> Apparently there appears to be another different similar lockup,
> >> The MTBF
On Tue, 2007-05-29 at 12:16 -0500, Roger Heflin wrote:
> Dave,
>
> Apparently there appears to be another different similar lockup,
> The MTBF has risen from 1-2 hours without that patch to >100 hours,
> so I am fairly sure the patch did correct the original lockup, or
> at the very least make
On Tue, 2007-05-29 at 12:16 -0500, Roger Heflin wrote:
Dave,
Apparently there appears to be another different similar lockup,
The MTBF has risen from 1-2 hours without that patch to 100 hours,
so I am fairly sure the patch did correct the original lockup, or
at the very least make it a lot
On Tue, 2007-05-29 at 13:14 -0500, Roger Heflin wrote:
Dave Kleikamp wrote:
On Tue, 2007-05-29 at 12:16 -0500, Roger Heflin wrote:
Dave,
Apparently there appears to be another different similar lockup,
The MTBF has risen from 1-2 hours without that patch to 100 hours,
so I am
On Thu, 2007-05-24 at 02:06 +0800, coly wrote:
> The patch is generated based on 2.6.20-ext4-2 branch. you can find the
> benchmark from other email.
>
> DO NOT waste time on reading the patch :-) I post this patch here is to
> show that I really spent time on it and the patch can work (even not
On Thu, 2007-05-24 at 02:06 +0800, coly wrote:
The patch is generated based on 2.6.20-ext4-2 branch. you can find the
benchmark from other email.
DO NOT waste time on reading the patch :-) I post this patch here is to
show that I really spent time on it and the patch can work (even not
On Thu, 2007-05-17 at 09:37 -0500, Roger Heflin wrote:
> Dave Kleikamp wrote:
>
> >
> > I don't have an answer to an ext3 deadlock, but this looks like a jfs
> > problem that was recently fixed in linux-2.6.22-rc1. I had intended to
> > send it to the stable
On Thu, 2007-05-17 at 09:40 +1000, David Chinner wrote:
> On Wed, May 16, 2007 at 07:21:16AM -0500, Dave Kleikamp wrote:
> > On Wed, 2007-05-16 at 13:16 +1000, David Chinner wrote:
> > > Please don't make this always happen. c/mtime updates should be dependent
> >
On Thu, 2007-05-17 at 09:40 +1000, David Chinner wrote:
On Wed, May 16, 2007 at 07:21:16AM -0500, Dave Kleikamp wrote:
On Wed, 2007-05-16 at 13:16 +1000, David Chinner wrote:
Please don't make this always happen. c/mtime updates should be dependent
on the mode being used and whether
On Thu, 2007-05-17 at 09:37 -0500, Roger Heflin wrote:
Dave Kleikamp wrote:
I don't have an answer to an ext3 deadlock, but this looks like a jfs
problem that was recently fixed in linux-2.6.22-rc1. I had intended to
send it to the stable kernel after it was picked up in mainline
On Wed, 2007-05-16 at 13:16 +1000, David Chinner wrote:
> On Wed, May 16, 2007 at 01:33:59AM +0530, Amit K. Arora wrote:
> > Following changes were made to the previous version:
> > 1) Added description before sys_fallocate() definition.
> > 2) Return EINVAL for len<=0 (With new draft that
On Wed, 2007-05-16 at 13:16 +1000, David Chinner wrote:
On Wed, May 16, 2007 at 01:33:59AM +0530, Amit K. Arora wrote:
Following changes were made to the previous version:
1) Added description before sys_fallocate() definition.
2) Return EINVAL for len=0 (With new draft that Ulrich
to the log_redrive
queue and the jfsIO thread to be awakened after the thread releases
log_redrive_lock but before it sets its state to TASK_INTERRUPTIBLE.
The jfsIO thread should set the state before giving up the spinlock, so
the waking thread will really wake it.
Signed-off-by: Dave Kleikamp <[EM
uper.c 2007-05-14 11:15:29.0 +1000
> @@ -738,6 +738,7 @@ static const struct super_operations jfs
> };
>
> static struct export_operations jfs_export_operations = {
> + .get_dentry = jfs_get_dentry,
> .get_parent = jfs_get_parent,
> };
Looks sane. You can add
can add:
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED]
--
David Kleikamp
IBM Linux Technology Center
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
to the log_redrive
queue and the jfsIO thread to be awakened after the thread releases
log_redrive_lock but before it sets its state to TASK_INTERRUPTIBLE.
The jfsIO thread should set the state before giving up the spinlock, so
the waking thread will really wake it.
Signed-off-by: Dave Kleikamp [EMAIL PROTECTED
/jfs/jfs_logmgr.c |7 ---
fs/jfs/jfs_txnmgr.c |6 +++---
9 files changed, 38 insertions(+), 9 deletions(-)
through these ChangeSets:
Commit: 05ec9e26be1f668ccba4ca54d9a4966c6208c611
Author: Dave Kleikamp <[EMAIL PROTECTED]> Sat, 05 May 2007 14:24:05
On Tue, 2007-05-08 at 16:22 +0530, Amit K. Arora wrote:
> On Mon, May 07, 2007 at 10:24:37AM -0500, Dave Kleikamp wrote:
> > On Mon, 2007-05-07 at 17:37 +0530, Amit K. Arora wrote:
> > > On Thu, May 03, 2007 at 09:31:33PM -0700, Andrew Morton wrote:
> > > > S
On Tue, 2007-05-08 at 16:22 +0530, Amit K. Arora wrote:
On Mon, May 07, 2007 at 10:24:37AM -0500, Dave Kleikamp wrote:
On Mon, 2007-05-07 at 17:37 +0530, Amit K. Arora wrote:
On Thu, May 03, 2007 at 09:31:33PM -0700, Andrew Morton wrote:
So we don't implement fallocate on bitmap-based
/jfs/jfs_logmgr.c |7 ---
fs/jfs/jfs_txnmgr.c |6 +++---
9 files changed, 38 insertions(+), 9 deletions(-)
through these ChangeSets:
Commit: 05ec9e26be1f668ccba4ca54d9a4966c6208c611
Author: Dave Kleikamp [EMAIL PROTECTED] Sat, 05 May 2007 14:24:05 -0500
On Mon, 2007-05-07 at 17:37 +0530, Amit K. Arora wrote:
> On Thu, May 03, 2007 at 09:31:33PM -0700, Andrew Morton wrote:
> > On Thu, 26 Apr 2007 23:43:32 +0530 "Amit K. Arora" <[EMAIL PROTECTED]>
> > wrote:
> > > +int ext4_fallocate(struct inode *inode, int mode, loff_t offset, loff_t
> > >
801 - 900 of 1013 matches
Mail list logo
