From: David Hildenbrand <david@redhat.com>
To: Christoph Hellwig <hch@lst.de>, jgg@ziepe.ca, akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm: remove mmu_notifier_get
Date: Wed, 16 Sep 2020 14:33:20 +0200 [thread overview]
Message-ID: <e4afb36e-68eb-c938-b8a2-9d5877e2d4aa@redhat.com> (raw)
In-Reply-To: <20200916112724.2174759-1-hch@lst.de>
On 16.09.20 13:27, Christoph Hellwig wrote:
> Remove the unused mmu_notifier_get inline function.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> include/linux/mmu_notifier.h | 10 ----------
> 1 file changed, 10 deletions(-)
>
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index b8200782dedeb9..acd1cc41f25d81 100644
> --- a/include/linux/mmu_notifier.h
> +++ b/include/linux/mmu_notifier.h
> @@ -279,16 +279,6 @@ static inline int mm_has_notifiers(struct mm_struct *mm)
>
> struct mmu_notifier *mmu_notifier_get_locked(const struct mmu_notifier_ops *ops,
> struct mm_struct *mm);
> -static inline struct mmu_notifier *
> -mmu_notifier_get(const struct mmu_notifier_ops *ops, struct mm_struct *mm)
> -{
> - struct mmu_notifier *ret;
> -
> - mmap_write_lock(mm);
> - ret = mmu_notifier_get_locked(ops, mm);
> - mmap_write_unlock(mm);
> - return ret;
> -}
> void mmu_notifier_put(struct mmu_notifier *subscription);
> void mmu_notifier_synchronize(void);
The doc of mmu_notifier_get_locked() has a reference to this function.
"Each call to mmu_notifier_get() must be paired with a call to
mmu_notifier_put()." - that should have been mmu_notifier_get_locked(),
maybe fix that up right away.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-09-16 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 11:27 Christoph Hellwig
2020-09-16 12:33 ` David Hildenbrand [this message]
2020-09-16 15:53 ` Jason Gunthorpe
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=e4afb36e-68eb-c938-b8a2-9d5877e2d4aa@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=linux-mm@kvack.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