All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: Patches for v4.4.y, v4.9.y, and v4.14.y to address rbtree test failures
Date: Fri, 14 Dec 2018 09:06:43 +0100	[thread overview]
Message-ID: <20181214080643.GA12329@kroah.com> (raw)
In-Reply-To: <1e712ab5-74f6-077e-af82-117f4b856f22@roeck-us.net>

On Thu, Dec 13, 2018 at 09:22:07PM -0800, Guenter Roeck wrote:
> Hi folks,
> 
> I recently started seeing spurious test failures with rbtree tests,
> resulting in boot delays and random "hung task" warnings.
> The problems have been fixed upstream with the following patches.
> 
> v4.14.y:
> 
> 0b548e33e6cb lib/rbtree-test: lower default params
> 
> v4.4.y, v4.9.y:
> 
> a54dae0338b7 lib/interval_tree_test.c: make test options module parameters
> c46ecce431eb lib/interval_tree_test.c: allow full tree search

Wait, this patch breaks the build for 4.4.y and 4.9.y, so this isn't
going to work well:

lib/interval_tree_test.c: In function ‘interval_tree_test_init’:
lib/interval_tree_test.c:105:38: error: ‘max_endpoint’ undeclared (first use in this function); did you mean ‘tracepoint’?
    unsigned long last = search_all ? max_endpoint : queries[j];
                                      ^~~~~~~~~~~~
                                      tracepoint


So I'm going to drop these from the 4.4 and 4.9 and 3.18 trees.  How did they
build for you?

confused,

greg k-h

  parent reply	other threads:[~2018-12-14  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  5:22 Patches for v4.4.y, v4.9.y, and v4.14.y to address rbtree test failures Guenter Roeck
2018-12-14  7:03 ` Greg Kroah-Hartman
2018-12-14  8:06 ` Greg Kroah-Hartman [this message]
2018-12-14 14:19   ` Guenter Roeck
2018-12-17 22:56     ` Sasha Levin
2018-12-18  1:38       ` Guenter Roeck

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=20181214080643.GA12329@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@roeck-us.net \
    --cc=sashal@kernel.org \
    --cc=stable@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.