From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org,
syzbot <syzbot+705209281e36404998f6@syzkaller.appspotmail.com>,
Peter Xu <peterx@redhat.com>,
David Hildenbrand <david@redhat.com>,
aarcange@redhat.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel BUG in move_pages
Date: Fri, 12 Jan 2024 13:57:25 +1100 [thread overview]
Message-ID: <20240112135725.2038ea89@canb.auug.org.au> (raw)
In-Reply-To: <CAJuCfpFxoDzQ_MBQe127pdWBRxugN2c7QsoemvHp+qCnfir+JQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hi all,
On Thu, 11 Jan 2024 17:44:57 -0800 Suren Baghdasaryan <surenb@google.com> wrote:
>
> I posted a quick fix for this issue here:
> https://lore.kernel.org/all/20240112013935.1474648-1-surenb@google.com/
> It cleanly applies over linux-next, mm-stable and mm-unstable. Andrew,
> Stephen, could you please pull the fix into your branches?
Since I will be away for a few days, I have applied that to linux-next today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-12 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 16:25 syzbot
2024-01-11 16:40 ` Suren Baghdasaryan
2024-01-11 16:44 ` Suren Baghdasaryan
2024-01-11 18:34 ` Suren Baghdasaryan
2024-01-11 18:58 ` David Hildenbrand
2024-01-11 20:20 ` Suren Baghdasaryan
[not found] ` <bf9dbc58-35c4-4a35-b194-6d8d9e7e4923@redhat.com>
2024-01-11 21:04 ` Suren Baghdasaryan
[not found] ` <15ce90cd-ff0b-4bc3-bee4-880bee3200ae@redhat.com>
2024-01-11 21:13 ` Suren Baghdasaryan
2024-01-11 23:23 ` Suren Baghdasaryan
2024-01-12 1:44 ` Suren Baghdasaryan
2024-01-12 2:57 ` Stephen Rothwell [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=20240112135725.2038ea89@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=surenb@google.com \
--cc=syzbot+705209281e36404998f6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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