All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
	oe-kbuild-all@lists.linux.dev,
	 Christian Brauner <christianvanbrauner@gmail.com>
Subject: Re: [brauner-vfs:vfs-6.15.misc 2/3] mm/gup.c:2270: warning: Function parameter or struct member 'locked' not described in 'get_dump_page'
Date: Wed, 5 Feb 2025 14:50:07 +0100	[thread overview]
Message-ID: <20250205-tomaten-getextet-8ccae3fc96c9@brauner> (raw)
In-Reply-To: <CAGudoHFOAD00iEjGSjbXeVz0F1xxyybANvo+LS-442Jn5NcuSQ@mail.gmail.com>

On Wed, Feb 05, 2025 at 01:35:26PM +0100, Mateusz Guzik wrote:
> On Wed, Feb 5, 2025 at 1:20 PM kernel test robot <lkp@intel.com> wrote:
> >
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.15.misc
> > head:   625aec60ff1462a0620753deeec4a38ddd032e29
> > commit: 62801d0e24907a20b4724b58ce174bc9a2fc3b4c [2/3] fs: avoid mmap sem relocks when coredumping with many missing pages
> > config: i386-buildonly-randconfig-003-20250205 (https://download.01.org/0day-ci/archive/20250205/202502052058.brmQ0100-lkp@intel.com/config)
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250205/202502052058.brmQ0100-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202502052058.brmQ0100-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> > >> mm/gup.c:2270: warning: Function parameter or struct member 'locked' not described in 'get_dump_page'
> >
> 
> how about this:
> 
> diff --git a/mm/gup.c b/mm/gup.c
> index 3883b307780e..66d2aec76d99 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -2254,6 +2254,7 @@ EXPORT_SYMBOL(fault_in_readable);
>  /**
>   * get_dump_page() - pin user page in memory while writing it to core dump
>   * @addr: user address
> + * @locked: a pointer to an int denoting whether the mmap sem is held
>   *
>   * Returns struct page pointer of user page pinned for dump,
>   * to be freed afterwards by put_page().
> 
> I presume I can avoid sending a full v2 :)

Yes, I already folded your fix. :)

      reply	other threads:[~2025-02-05 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 12:20 [brauner-vfs:vfs-6.15.misc 2/3] mm/gup.c:2270: warning: Function parameter or struct member 'locked' not described in 'get_dump_page' kernel test robot
2025-02-05 12:35 ` Mateusz Guzik
2025-02-05 13:50   ` Christian Brauner [this message]

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=20250205-tomaten-getextet-8ccae3fc96c9@brauner \
    --to=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=lkp@intel.com \
    --cc=mjguzik@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.