From: Jens Axboe <axboe@kernel.dk>
To: Martin Pirker <lkml.collector@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35-rc5 inconsistent lock state
Date: Sun, 18 Jul 2010 18:39:49 -0600 [thread overview]
Message-ID: <4C439ED5.8010002@kernel.dk> (raw)
In-Reply-To: <AANLkTikk_UNVoo9CC9DhCSwiI5mEB3j1RrXqqOPdei1L@mail.gmail.com>
On 07/18/2010 11:56 AM, Martin Pirker wrote:
> On Sat, Jul 17, 2010 at 9:50 PM, Jens Axboe <axboe@kernel.dk> wrote:
>> Can anyone try this completed untested patch?
>>
>> diff --git a/block/blk-core.c b/block/blk-core.c
>> index 5ab3ac2..a108b8e 100644
> ....
>
> /usr/src/linux-2.6.35-rc5 # patch -p1 <jens.patch
> patching file block/blk-core.c
> Hunk #1 FAILED at 451.
> Hunk #2 FAILED at 515.
> 2 out of 2 hunks FAILED -- saving rejects to file block/blk-core.c.rej
> patching file include/linux/backing-dev.h
> Hunk #1 FAILED at 84.
> 1 out of 1 hunk FAILED -- saving rejects to file include/linux/backing-dev.h.rej
> patching file include/linux/writeback.h
> patching file mm/page-writeback.c
> Hunk #1 FAILED at 698.
> Hunk #2 FAILED at 719.
> Hunk #3 FAILED at 739.
> 3 out of 3 hunks FAILED -- saving rejects to file mm/page-writeback.c.rej
>
>
> ummmm.... help?
Oh, the patch is for the next branches. I'll see if I can fiddle it into
.35-rcX
--
Jens Axboe
next prev parent reply other threads:[~2010-07-19 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 20:33 2.6.35-rc5 inconsistent lock state Martin Pirker
2010-07-14 21:04 ` Rafael J. Wysocki
2010-07-17 19:04 ` Dan Carpenter
2010-07-17 19:50 ` Jens Axboe
2010-07-18 17:56 ` Martin Pirker
2010-07-19 0:39 ` Jens Axboe [this message]
2010-07-19 0:42 ` Jens Axboe
2010-07-19 19:48 ` Martin Pirker
2010-09-03 7:37 ` Florian Mickler
2010-09-04 7:17 ` Jens Axboe
2010-09-04 8:48 ` Florian Mickler
2010-07-15 17:38 ` Maciej Rutecki
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=4C439ED5.8010002@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.collector@gmail.com \
/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