From: Byungchul Park <max.byungchul.park@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
david@fromorbit.com, willy@infradead.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Amir Goldstein <amir73il@gmail.com>,
byungchul.park@lge.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, oleg@redhat.com
Subject: Re: About the try to remove cross-release feature entirely by Ingo
Date: Thu, 14 Dec 2017 22:30:24 +0900 [thread overview]
Message-ID: <CANrsvRP8hHUJZAYUnJ5Vbu79O+HRrWfWou=Q0stRiLO9SaidCw@mail.gmail.com> (raw)
In-Reply-To: <20171214111817.xnyxgtremfspjk7f@hirez.programming.kicks-ass.net>
On Thu, Dec 14, 2017 at 8:18 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Dec 13, 2017 at 10:07:11PM -0500, Theodore Ts'o wrote:
>> interpreted this as the lockdep maintainers saying, "hey, not my
>> fault, it's the subsystem maintainer's fault for not properly
>> classifying the locks" --- and thus dumping the responsibility in the
>> subsystem maintainers' laps.
>
> Let me clarify that I (as lockdep maintainer) disagree with that
> sentiment. I have spend a lot of time over the years staring at random
> code trying to fix lockdep splats. Its awesome if corresponding
> subsystem maintainers help out and many have, but I very much do not
> agree its their problem and their problem alone.
I apologize to all of you. That's really not what I intended to say.
I said that other folks can annotate it for the sub-system better
than lockdep developer, so suggested to invalidate locks making
trouble and wanting to avoid annotating it at the moment, and
validate those back when necessary with additional annotations.
It's my fault. I'm not sure how I should express what I want to say,
but, I didn't intend to charge the responsibility to other folks.
Ideally, I think it's best to solve it with co-work. I should've been
more careful to say that.
Again, I apologize for that, to lockdep and fs maintainers.
Of course, for cross-release, I have the will to annotate it or
find a better way to avoid false positives. And I think I have to.
--
Thanks,
Byungchul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-14 13:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 6:24 Byungchul Park
2017-12-13 7:13 ` Byungchul Park
2017-12-13 15:23 ` Bart Van Assche
2017-12-14 3:07 ` Theodore Ts'o
2017-12-14 5:58 ` Byungchul Park
2017-12-14 11:18 ` Peter Zijlstra
2017-12-14 13:30 ` Byungchul Park [this message]
2017-12-13 10:46 ` [PATCH] locking/lockdep: Remove the cross-release locking checks Ingo Molnar
2017-12-14 5:01 ` Byungchul Park
2017-12-15 4:05 ` Byungchul Park
2017-12-15 6:24 ` Theodore Ts'o
2017-12-15 7:38 ` Byungchul Park
2017-12-15 8:39 ` Byungchul Park
2017-12-15 21:15 ` Theodore Ts'o
2017-12-16 2:41 ` Byungchul Park
2017-12-29 1:47 ` About the try to remove cross-release feature entirely by Ingo Byungchul Park
2017-12-29 2:02 ` Byungchul Park
2017-12-29 3:51 ` Theodore Ts'o
2017-12-29 7:28 ` Byungchul Park
2017-12-30 6:16 ` Matthew Wilcox
2017-12-30 15:40 ` Theodore Ts'o
2017-12-30 20:44 ` Matthew Wilcox
2017-12-30 22:40 ` Theodore Ts'o
2017-12-30 23:00 ` Theodore Ts'o
2018-01-01 10:18 ` Matthew Wilcox
2018-01-01 16:00 ` Theodore Ts'o
2018-01-03 2:38 ` Byungchul Park
2018-01-03 2:28 ` Byungchul Park
2018-01-03 2:58 ` Dave Chinner
2018-01-03 5:48 ` Byungchul Park
2018-01-05 16:49 ` J. Bruce Fields
2018-01-05 17:05 ` J. Bruce Fields
2018-01-03 2:10 ` Byungchul Park
2018-01-03 7:05 ` Theodore Ts'o
2018-01-03 8:10 ` Byungchul Park
2018-01-03 8:23 ` Byungchul Park
2018-01-03 1:57 ` Byungchul Park
2018-01-02 7:57 ` Byungchul Park
2017-12-29 8:09 ` Amir Goldstein
2017-12-29 9:46 ` Byungchul Park
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='CANrsvRP8hHUJZAYUnJ5Vbu79O+HRrWfWou=Q0stRiLO9SaidCw@mail.gmail.com' \
--to=max.byungchul.park@gmail.com \
--cc=amir73il@gmail.com \
--cc=byungchul.park@lge.com \
--cc=david@fromorbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox