[<prev] [next>] [day] [month] [year] [list]
Message-ID: <1307291187.8545.41.camel@t41.thuisdomein>
Date: Sun, 05 Jun 2011 18:26:18 +0200
From: Paul Bolle <pebolle@...cali.nl>
To: Jens Axboe <axboe@...nel.dk>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, Vivek Goyal <vgoyal@...hat.com>
Subject: [PATCH 0/5] Demystified CFQ Oops
This is a set of five commits that should demystify a CFQ Oops that I
was able to easily trigger on a laptop I use. (It is actually still
unclear why it was exactly so easy for me to trigger it on that laptop.)
This set contains one trivial fix, three clean-ups and one commit that
should actually fix this issue. The clean-ups were essential in helping
pinpoint the problem and should make review a lot easier.
Review of the last patch - which covers stuff rather unfamiliar to me -
would be especially appreciated.
I must admit that, while finalizing this set, I have not tested that the
set is cleanly bisectable (ie, that all commits lead to a tree that at
least builds). I could still do that, but perhaps there's someone with
more experience and especially with (much) more powerful hardware for
whom that would be much easier to do than for me.
Paul Bolle (5):
CFQ: make two functions static
Rename two struct members called "cic_list"
CFQ: rename ioc_data to last_cic
block: rename the return of two functions
CFQ: use proper locking for cache of last hit cic
block/blk-ioc.c | 50 ++++++++++++++++++++++----------------------
block/cfq-iosched.c | 49 +++++++++++++++++++++++++++-----------------
include/linux/iocontext.h | 6 ++--
3 files changed, 58 insertions(+), 47 deletions(-)
--
1.7.5.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists