linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chanho Park" <chanho61.park@samsung.com>
To: "'Marek Szyprowski'" <m.szyprowski@samsung.com>, <axboe@kernel.dk>
Cc: <sfr@canb.auug.org.au>, <linux-block@vger.kernel.org>,
	<linux-next@vger.kernel.org>
Subject: RE: Regression of next-20211019
Date: Wed, 20 Oct 2021 17:18:45 +0900	[thread overview]
Message-ID: <00fa01d7c58b$19edcd60$4dc96820$@samsung.com> (raw)
In-Reply-To: <ce5dcc95-8609-b1d9-81a0-f8d6cd6a3e7b@samsung.com>

Hi Marek,

> > I found a NULL pointer dereference on next-20211019. It might be a
> > regression since next-20211015.
> > So, I did "git bisect" and found below commit. Are you already aware
> > of this?
> 
> I also found this issue in yesterday's linux-next. Then I found that is
> has been already fixed by this patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
> block.git/commit/?h=for-next&id=3039417eec780c6bbb119ae5598fdca2d4a957ec
> so I decided that there is no point in reporting it.
> 
> In today's linux-next it has been fixed by the commit
> https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
> block.git/commit/?h=for-next&id=e70feb8b3e6886c525c88943b5f1508d02f5a683

Great. It works for me. I should use today's version.

Best Regards,
Chanho Park


      reply	other threads:[~2021-10-20  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20211020073900epcas2p402043934d4ca8f04113bc5ce50d2f596@epcas2p4.samsung.com>
2021-10-20  7:39 ` Regression of next-20211019 Chanho Park
2021-10-20  8:07   ` Marek Szyprowski
2021-10-20  8:18     ` Chanho Park [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='00fa01d7c58b$19edcd60$4dc96820$@samsung.com' \
    --to=chanho61.park@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sfr@canb.auug.org.au \
    /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).