From: Jens Axboe <axboe@kernel.dk>
To: Andrey Wagin <avagin@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Cc: Arianna Avanzini <avanzini.arianna@gmail.com>
Subject: Re: linux-next: BUG: unable to handle kernel NULL pointer dereference in cfq_print_leaf_weight()
Date: Fri, 19 Jun 2015 10:24:10 -0600 [thread overview]
Message-ID: <5584422A.8050009@kernel.dk> (raw)
In-Reply-To: <CANaxB-zEpB26kNRdthoZjz04ZQmXycByK8hRfQDes+K1i0_eJw@mail.gmail.com>
On 06/17/2015 03:55 PM, Andrey Wagin wrote:
> Hi All,
>
> I executed CRIU tests on the 4.1.0-rc8-next-20150617 kernel and met
> this bug. Maybe it will be interested for someone to look at it.
This should fix it:
http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.2/core&id=9470e4a693db84bee7becbba8de01af02bb23c9f
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-19 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 21:55 linux-next: BUG: unable to handle kernel NULL pointer dereference in cfq_print_leaf_weight() Andrey Wagin
2015-06-18 21:09 ` Andrey Wagin
2015-06-19 16:24 ` Jens Axboe [this message]
2015-06-19 20:26 ` Andrey Wagin
2015-06-22 20:13 ` Andrey Wagin
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=5584422A.8050009@kernel.dk \
--to=axboe@kernel.dk \
--cc=avagin@gmail.com \
--cc=avanzini.arianna@gmail.com \
--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.