From: Andy Whitcroft <apw@shadowen.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Mariusz Kozlowski <m.kozlowski@tuxland.pl>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc6-mm1
Date: Thu, 23 Nov 2006 20:20:40 +0000 [thread overview]
Message-ID: <45660298.3090003@shadowen.org> (raw)
In-Reply-To: <20061123103607.af7ae8b0.akpm@osdl.org>
Andrew Morton wrote:
> On Thu, 23 Nov 2006 12:23:48 +0100
> Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
>
>> Hello,
>>
>> Hmmm ... didn't apply cleanly.
>>
>> patching file kernel/tsacct.c
>> Hunk #1 FAILED at 97.
>> 1 out of 1 hunk FAILED -- saving rejects to file kernel/tsacct.c.rej
>
> I think your local tree is not clean.
I get this accross the board on my test system too. All clean downloads.
A quick look at the combo-patch and the broken-out patch seems to
indicate they are not in sync with each other. In the combo-patch we
have this hunk (which is the one which fails):
--- linux-2.6.19-rc6/kernel/tsacct.c 2006-11-16 23:19:32.000000000 -0800
+++ devel/kernel/tsacct.c 2006-11-23 01:12:17.000000000 -0800
@@ -97,7 +97,14 @@ void xacct_add_tsk(struct taskstats *sta
stats->read_syscalls = p->syscr;
stats->write_syscalls = p->syscw;
#ifdef CONFIG_TASK_IO_ACCOUNTING
- stats->read_bytes = p->ioac->read_bytes
+ stats->read_bytes = p->ioac.read_bytes;
+ stats->write_bytes = p->ioac.write_bytes;
+ stats->cancelled_write_bytes = p->ioac.cancelled_write_bytes;
+#else
+ stats->read_bytes = 0;
+ stats->write_bytes = 0;
+ stats->cancelled_write_bytes = 0;
+#endif
In the broken-out directory the only patch which references this file
has the following different hunk:
--- a/kernel/tsacct.c~io-accounting-via-taskstats
+++ a/kernel/tsacct.c
@@ -96,6 +96,15 @@ void xacct_add_tsk(struct taskstats *sta
stats->write_char = 0;
stats->read_syscalls = p->syscr;
stats->write_syscalls = p->syscw;
+#ifdef CONFIG_TASK_IO_ACCOUNTING
+ stats->read_bytes = p->ioac.read_bytes;
+ stats->write_bytes = p->ioac.write_bytes;
+ stats->cancelled_write_bytes = p->ioac.cancelled_write_bytes;
+#else
+ stats->read_bytes = 0;
+ stats->write_bytes = 0;
+ stats->cancelled_write_bytes = 0;
+#endif
}
#undef KB
#undef MB
Looking at 2.6.19-rc6 this second version seems completely reasonable.
The former does not.
-apw
next prev parent reply other threads:[~2006-11-23 20:20 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 10:17 2.6.19-rc6-mm1 Andrew Morton
2006-11-23 10:38 ` 2.6.19-rc6-mm1 Reuben Farrelly
2006-11-23 14:06 ` [PATCH] x86_64: fix build without HOTPLUG_CPU (was Re: 2.6.19-rc6-mm1) Jiri Kosina
2006-11-23 15:08 ` Andi Kleen
2006-11-23 15:17 ` Jiri Kosina
2006-11-23 15:27 ` Andi Kleen
2006-11-23 15:37 ` Jiri Kosina
2006-11-23 16:33 ` Ingo Molnar
2006-11-23 11:23 ` 2.6.19-rc6-mm1 Mariusz Kozlowski
2006-11-23 18:36 ` 2.6.19-rc6-mm1 Andrew Morton
2006-11-23 19:24 ` 2.6.19-rc6-mm1 Mariusz Kozlowski
2006-11-23 20:20 ` Andy Whitcroft [this message]
2006-11-23 20:56 ` 2.6.19-rc6-mm1 Andrew Morton
2006-11-24 19:34 ` 2.6.19-rc6-mm1 Matthew Frost
2006-11-23 20:23 ` 2.6.19-rc6-mm1 Benoit Boissinot
2006-11-23 12:22 ` 2.6.19-rc6-mm1 Mariusz Kozlowski
2006-11-23 13:03 ` 2.6.19-rc6-mm1 Andy Whitcroft
2006-11-23 17:26 ` MCORE2 include/asm/module.h:60:2: error: #error unknown processor family [was Re: 2.6.19-rc6-mm1] Mattia Dongili
2006-11-23 23:30 ` 2.6.19-rc6-mm1: no help text for TCP_MD5SIG_DEBUG Adrian Bunk
2006-11-24 1:37 ` David Miller
2006-11-24 0:17 ` 2.6.19-rc6-mm1: drivers/net/chelsio/: unused code Adrian Bunk
2006-11-27 18:24 ` Stephen Hemminger
2006-11-29 7:36 ` Adrian Bunk
2006-11-29 7:47 ` Andrew Morton
2007-02-20 0:02 ` Adrian Bunk
2007-02-20 21:31 ` Stephen Hemminger
2007-02-20 22:06 ` Adrian Bunk
2006-11-24 1:46 ` [-mm patch] make qla2x00_reg_remote_port() static Adrian Bunk
2006-11-27 17:22 ` Andrew Vasquez
2006-11-24 1:46 ` [-mm patch] make proc_pid_io_accounting() static Adrian Bunk
2006-11-24 1:46 ` [-mm patch] make readahead_debug_level static Adrian Bunk
2006-11-24 16:59 ` [PATCH] efi_limit_regions triggers link failure when CONFIG_EFI is not defined Andy Whitcroft
2006-11-24 17:05 ` Andi Kleen
2006-11-24 17:24 ` Andy Whitcroft
2006-11-24 17:33 ` Andi Kleen
2006-11-24 21:30 ` Andrew Morton
2006-11-26 2:13 ` Matthew Frost
2006-11-24 17:58 ` [PATCH] x86_64 vsyscall fails to compile when CONFIG_HOTPLUG_CPU is disabled Andy Whitcroft
2006-11-24 18:03 ` Jiri Kosina
2006-11-24 19:11 ` Andi Kleen
2006-11-24 21:58 ` [-mm patch] net/: possible cleanups Adrian Bunk
2006-12-01 1:28 ` David Miller
2006-11-25 19:15 ` [-mm patch] include/linux/bug.h must always #include <linux/module.h> Adrian Bunk
2006-11-25 19:17 ` [-mm patch] fs/stack.c should #include <linux/fs_stack.h> Adrian Bunk
2006-11-25 19:57 ` Josef Sipek
2006-11-25 19:21 ` [-mm patch] fs/reiser4/: more possible cleanups Adrian Bunk
2006-11-25 19:48 ` 2.6.19-rc6-mm1 -- sched-improve-migration-accuracy.patch slows boot Don Mullis
2006-11-26 6:24 ` Mike Galbraith
2006-11-27 1:38 ` Don Mullis
2006-11-27 10:16 ` Ingo Molnar
2006-11-28 18:47 ` Don Mullis
2006-11-27 10:50 ` [patch] " Mike Galbraith
2006-11-27 17:17 ` Don Mullis
2006-11-27 18:27 ` Mike Galbraith
2006-11-26 5:40 ` [-mm patch] sound/soc/soc-dapm.c: make 4 functions static Adrian Bunk
2006-11-27 4:21 ` [PATCH] paravirt reorder functions to avoid unspecified behaviour Andy Whitcroft
2006-11-27 11:13 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45660298.3090003@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox