mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: kernel-team@lge.com, LKML <linux-kernel@vger.kernel.org>
Subject: [QUESTION] Bringing cross-release back to be alive
Date: Tue, 27 Feb 2018 17:26:00 +0900	[thread overview]
Message-ID: <8c535191-e24d-6465-e809-81ae9e9b23e0@lge.com> (raw)

Hello,

Cross-release introduced a false positive in some fs configs,
which was too hard to solve fundamentally - which requires to
distinguish between all dynamic instances.

I also think it better be removed than making fs developers
disable whole lockdep. But I believe that it's still helpful
in the rest of the configs.

Therefore, I want to bring it back after preventing bothering
them. I think we can achieve it by invalidating problematic
waiters at the moment producing a false positive and letting
them worked out finely later.

For example, in the case where we got trouble in, we can
initialize the completion in submit_bio_wait() with no-map
version. That way, we can achieve our goal easily for all
problems caused by cross-release in the future.

Of course, it would be the best if we solve the problems in a
right way later, but just leaving them invalidated would be
also fine because the cases are exactly same as before
applying cross-release.

I'm curious about what you think about that. If you say yes,
then I will re-summit after adding the work I mentioned above.

-- 
Thanks,
Byungchul

                 reply	other threads:[~2018-02-27  8:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8c535191-e24d-6465-e809-81ae9e9b23e0@lge.com \
    --to=byungchul.park@lge.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®