All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Guangwu Zhang <guazhang@redhat.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
	fstests@vger.kernel.org
Subject: Re: [bug report] Internal error isnullstartblock(got.br_startblock) a t line 6005 of file fs/xfs/libxfs/xfs_bmap.c.
Date: Mon, 20 May 2024 20:16:41 -0600	[thread overview]
Message-ID: <8b4f7d90-05d9-4245-889f-64c86bd81e98@kernel.dk> (raw)
In-Reply-To: <CAGS2=YqCD15RVtZ=NWVjPMa22H3wks1z6TSMVk7jmE_k1A-csg@mail.gmail.com>

On 5/20/24 7:05 PM, Guangwu Zhang wrote:
> yes,
> the branch header info.
> commit 04d3822ddfd11fa2c9b449c977f340b57996ef3d
> Merge: 59ef81807482 7b815817aa58
> Author: Jens Axboe <axboe@kernel.dk>
> Date:   Fri May 17 09:40:38 2024 -0600
> 
>     Merge branch 'block-6.10' into for-next
> 
>     * block-6.10:
>       blk-mq: add helper for checking if one CPU is mapped to specified hctx

Doesn't reproduce for me, with many loops on either nvme or SCSI. You seem
to be using loop, can you please include some more details on your setup?

-- 
Jens Axboe



  reply	other threads:[~2024-05-21  2:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 11:48 [bug report] Internal error isnullstartblock(got.br_startblock) a t line 6005 of file fs/xfs/libxfs/xfs_bmap.c Guangwu Zhang
2024-05-20 15:09 ` Christoph Hellwig
2024-05-21  1:05   ` Guangwu Zhang
2024-05-21  2:16     ` Jens Axboe [this message]
2024-05-21  5:05 ` Zhang Yi
2024-05-21 10:06   ` Guangwu Zhang
2024-05-21 11:57     ` Zhang Yi
2024-05-22  0:46       ` Guangwu Zhang

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=8b4f7d90-05d9-4245-889f-64c86bd81e98@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fstests@vger.kernel.org \
    --cc=guazhang@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-xfs@vger.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.