linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Igor Pylypiv <ipylypiv@google.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	Changyuan Lyu <changyuanl@google.com>
Subject: Re: [PATCH] Revert "module, async: async_synchronize_full() on module init iff async is used"
Date: Tue, 1 Feb 2022 07:50:08 -1000	[thread overview]
Message-ID: <Yfly0P4e84373mGF@slm.duckdns.org> (raw)
In-Reply-To: <YflxP28HlVrrNBU2@slm.duckdns.org>

On Tue, Feb 01, 2022 at 07:43:27AM -1000, Tejun Heo wrote:
> That's quite a walk down the memory lane and I agree with your analysis. The
> PF_USED_ASYNC is redundant for correctness with the removal of synchrnous
> loading from iosched path and the WARN_ON guarantees that nothing in kernel
> is creating a similar situation.
> 
> Acked-by: Tejun Heo <tj@kernel.org>

BTW, I can route this through workqueue tree but -mm or going to Linus's
tree directly might be a better option. Any opinions?

Thanks.

-- 
tejun

  reply	other threads:[~2022-02-01 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 23:39 [PATCH] Revert "module, async: async_synchronize_full() on module init iff async is used" Igor Pylypiv
2022-01-28  7:39 ` Linus Torvalds
2022-01-31 21:58   ` Igor Pylypiv
2022-02-01 18:13   ` Tejun Heo
2022-02-01 18:20     ` Greg Kroah-Hartman
2022-02-01 17:43 ` Tejun Heo
2022-02-01 17:50   ` Tejun Heo [this message]
2022-02-03  1:11     ` Luis Chamberlain
2022-02-03 19:19     ` Linus Torvalds

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=Yfly0P4e84373mGF@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=changyuanl@google.com \
    --cc=ipylypiv@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).