All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: syzbot <syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com>,
	Liam.Howlett@oracle.com, akpm@linux-foundation.org,
	david@kernel.org, jannh@google.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, ljs@kernel.org, riel@surriel.com,
	syzkaller-bugs@googlegroups.com, vbabka@kernel.org,
	peterx@redhat.com
Subject: Re: [syzbot] [mm?] WARNING in folio_add_new_anon_rmap
Date: Mon, 16 Mar 2026 13:01:57 +0200	[thread overview]
Message-ID: <abfjJYAWOLpsQuq5@kernel.org> (raw)
In-Reply-To: <abehBY7QakYF9bK4@hyeyoo>

Hi Harry,

Thanks for the fix :)

@Andrew, can you please fold it into
"userfaultfd: introduce struct mfill_state"

On Mon, Mar 16, 2026 at 03:19:49PM +0900, Harry Yoo wrote:
> #syz test
> 
> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
> index 510c6dcb9824..73adf9ffcac2 100644
> --- a/mm/userfaultfd.c
> +++ b/mm/userfaultfd.c
> @@ -880,7 +880,7 @@ static __always_inline ssize_t mfill_atomic(struct userfaultfd_ctx *ctx,
>  		.dst_start = dst_start,
>  		.src_start = src_start,
>  		.flags = flags,
> -
> +		.len = len,
>  		.src_addr = src_start,
>  		.dst_addr = dst_start,
>  	};
> 

-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2026-03-16 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 19:09 [syzbot] [mm?] WARNING in folio_add_new_anon_rmap syzbot
2026-03-16  2:02 ` Forwarded: [PATCH] mm/userfaultfd: re-validate vma in mfill_atomic() loop under CONFIG_PER_VMA_LOCK syzbot
2026-03-16  5:11 ` Forwarded: [PATCH] mm/userfaultfd: validate dst_addr after re-acquiring VMA lock in mfill_copy_folio_retry syzbot
2026-03-16  6:19 ` [syzbot] [mm?] WARNING in folio_add_new_anon_rmap Harry Yoo
2026-03-16  6:58   ` syzbot
2026-03-16 11:01   ` Mike Rapoport [this message]
     [not found] <20260316020210.543036-1-kartikey406@gmail.com>
2026-03-16  2:40 ` syzbot
     [not found] <20260316051111.546771-1-kartikey406@gmail.com>
2026-03-16  6:00 ` syzbot

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=abfjJYAWOLpsQuq5@kernel.org \
    --to=rppt@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=harry.yoo@oracle.com \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=peterx@redhat.com \
    --cc=riel@surriel.com \
    --cc=syzbot+e24a2e34fad0efbac047@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vbabka@kernel.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 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.