From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Kevin Coffman" <kwc@citi.umich.edu>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-sha1: RIP [<ffffffff802596c8>] iov_iter_advance+0x38/0x70
Date: Tue, 4 Mar 2008 03:41:27 +1100 [thread overview]
Message-ID: <200803040341.28127.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <4d569c330803030530j76a47249ic4e3eb2d86283d6f@mail.gmail.com>
On Tuesday 04 March 2008 00:30, Kevin Coffman wrote:
> On Sun, Mar 2, 2008 at 11:38 PM, Nick Piggin <nickpiggin@yahoo.com.au>
> > Hmm, thanks for testing... Could it be caused by other bugs introduced
> > in the kernel you are testing? Is the failing test using writev to
> > write the file? Do you have any indication of the pattern of corruption?
>
> Well, all I did was apply your patch and re-run the same tests I've
> been running successfully. (I'm still sitting at 2.6.25-rc1 right
> now). Sorry, I don't have details about the corruption. I'm home
> sick today, but I'll try to get more details when I get back in the
> office.
OK my last patch had a silly thinko in it, sorry. I'll improve it
and retest it before asking you to do any more. Thanks so far..
next prev parent reply other threads:[~2008-03-03 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 14:00 2.6.24-sha1: RIP [<ffffffff802596c8>] iov_iter_advance+0x38/0x70 Alexey Dobriyan
2008-02-10 17:46 ` Alexey Dobriyan
2008-02-12 22:04 ` Andrew Morton
2008-02-12 22:27 ` Alexey Dobriyan
2008-02-13 0:17 ` Nick Piggin
2008-02-13 4:42 ` Nick Piggin
2008-02-19 20:47 ` Alexey Dobriyan
2008-02-19 22:01 ` Alexey Dobriyan
2008-02-26 3:46 ` Nick Piggin
2008-02-27 17:41 ` Kevin Coffman
2008-03-03 4:38 ` Nick Piggin
2008-03-03 13:30 ` Kevin Coffman
2008-03-03 16:41 ` Nick Piggin [this message]
2008-02-19 1:20 ` Nick Piggin
2008-02-19 19:22 ` Kevin Coffman
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=200803040341.28127.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kwc@citi.umich.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.