From: Jens Axboe <axboe@kernel.dk>
To: jonghwi.rha@samsung.com
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>, 김정태 <jt1217.kim@samsung.com>,
정혜연 <hyeon.chung@samsung.com>
Subject: Re: [Samsung] bsg-lib.c patch for double-free error fix.
Date: Wed, 4 Feb 2026 20:46:22 -0700 [thread overview]
Message-ID: <8c7399bf-76b3-4902-b257-b85c95543f6f@kernel.dk> (raw)
In-Reply-To: <20260202120425epcms2p481d034d2a8fc522819673f0bcd59cefd@epcms2p4>
On 2/2/26 5:04 AM, ??? wrote:
> Dear Jens,
>
> Sorry for the excuse, also thank you for the response.
>
> It was my first time with the procedure, so there was a mistake. I
> apologize for the inconvenience. As you mentioned, in the case of the
> previous patch, there was duplicate code, so changing it to kzalloc
> would indeed be meaningless.
>
> We have prepared a new patch and completed internal testing on our
> side. Without this patch, issues occur when using ufs-bsg.
This patch looks better. Can you please send it out as a separate email?
--
Jens Axboe
next prev parent reply other threads:[~2026-02-05 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260130091020epcms2p2d85af8781639a17ab517208feb270dbd@epcms2p4>
2026-02-02 12:04 ` Re: [Samsung] bsg-lib.c patch for double-free error fix 라종휘
2026-02-05 3:46 ` Jens Axboe [this message]
2026-02-05 5:32 ` [Patch] bsg: initialize request and reply payloads in bsg_prepare_job 라종휘
2026-02-05 13:42 ` Jens Axboe
2026-02-05 23:45 ` Hannes Reinecke
2026-02-06 4:58 ` 라종휘
[not found] <CGME20260112094010epcms2p518c5eb5408f90ceb7ef5739a0fbf7f65@epcms2p5>
[not found] ` <1591680112.4972876.1768210810254@v8mail-kr2-6.v8mail-kr2.knoxportal-kr-prod-blue.svc.cluster.local>
2026-01-12 15:36 ` [Samsung] bsg-lib.c patch for double-free error fix Jens Axboe
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=8c7399bf-76b3-4902-b257-b85c95543f6f@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=hyeon.chung@samsung.com \
--cc=jonghwi.rha@samsung.com \
--cc=jt1217.kim@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox