linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christian Brauner <brauner@kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org, lkft-triage@lists.linaro.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next: x86: RIP: 0010:do_iter_read+0x241/0x340 - BUG: unable to handle page fault for address: 000000000042da60
Date: Mon, 27 Mar 2023 09:46:17 -0600	[thread overview]
Message-ID: <c1fcc9c4-1409-0890-7032-c247c15097e5@kernel.dk> (raw)
In-Reply-To: <20230327075841.pblnllclg2idy3rp@wittgenstein>

On 3/27/23 1:58 AM, Christian Brauner wrote:
> +Jens for awareness because of
> 
> Subject: [PATCHSET 0/2] Turn single segment imports into ITER_UBUF
> https://lore.kernel.org/linux-fsdevel/20230324204443.45950-1-axboe@kernel.dk
> 
> which seems like a likely candidate.

It's certainly that. So odd, I even ran these test cases! I'll drop the series
from for-next for now and dig into this separately.

-- 
Jens Axboe



      reply	other threads:[~2023-03-27 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  6:17 next: x86: RIP: 0010:do_iter_read+0x241/0x340 - BUG: unable to handle page fault for address: 000000000042da60 Naresh Kamboju
2023-03-27  7:58 ` Christian Brauner
2023-03-27 15:46   ` Jens Axboe [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=c1fcc9c4-1409-0890-7032-c247c15097e5@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sfr@canb.auug.org.au \
    --cc=viro@zeniv.linux.org.uk \
    /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).