<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Guilherme,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We appreciate you letting us know. This is in the discretion of the publication chairs, Chenhao Ye and Duo Zhang (cc'ed), who handle the publication. They will have a better idea about whether the changes can be made: the proceedings may already be in the pipeline
for production. </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
-Bryan S. Kim</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Hotstorage-chairs <hotstorage-chairs-bounces@fsl.cs.sunysb.edu> on behalf of Guilherme Lima via Hotstorage-chairs <hotstorage-chairs@fsl.cs.sunysb.edu><br>
<b>Sent:</b> Monday, August 31, 2026 09:43<br>
<b>To:</b> chairs26@hotstorage.org <chairs26@hotstorage.org><br>
<b>Cc:</b> tmsasaki@prof.inteli.edu.br <tmsasaki@prof.inteli.edu.br><br>
<b>Subject:</b> [Hotstorage-chairs] Camera-ready correction request</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Dear Young-ri and Bryan,<br>
<br>
I have found an error in the camera-ready of our HotStorage '26 paper and I would<br>
like to correct it before the proceedings are published, if that is still possible.<br>
<br>
Paper: To Migrate or Not to Migrate: KOxI, an Evidence-Gated Pipeline for Rust-for-Linux<br>
Storage Drivers<br>
Authors: Guilherme Lima, Tomaz Mikio Sasaki (Instituto de Tecnologia e Liderança)<br>
DOI: 10.1145/3837053.3837340<br>
<br>
Reference [9] gives the wrong first author. It currently reads:<br>
<br>
[9] Zhuohua Li et al. 2024. Rust for Linux: Understanding the Security<br>
Impact of Rust in the Linux Kernel. In Annual Computer Security<br>
Applications Conference.<br>
<br>
The first author is Zhaofeng Li, not Zhuohua Li. Zhuohua Li is a different<br>
researcher who also publishes on Rust security, which is how I believe the error<br>
entered my bibliography.<br>
<br>
The correct reference is:<br>
<br>
[9] Zhaofeng Li, Vikram Narayanan, Xiangdong Chen, Jerry Zhang, and Anton Burtsev.<br>
2024. Rust for Linux: Understanding the Security Impact of Rust in the Linux<br>
Kernel. In 2024 Annual Computer Security Applications Conference (ACSAC),<br>
548-562. <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fdoi.org%2f10.1109%2fACSAC63791.2024.00054&c=E,1,P3hQ4JL-wwpfnHUTBnyoAsNCqg1_51P7HQGffSf-PTi6XhB_Y_tAhQhjUm-NXx3wijEsuHUX-7GMAGcFrnPozpuA9CtvEfdLWii7CaM9-lGF9_6tmtlblatCDO8,&typo=1">
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fdoi.org%2f10.1109%2fACSAC63791.2024.00054&c=E,1,P3hQ4JL-wwpfnHUTBnyoAsNCqg1_51P7HQGffSf-PTi6XhB_Y_tAhQhjUm-NXx3wijEsuHUX-7GMAGcFrnPozpuA9CtvEfdLWii7CaM9-lGF9_6tmtlblatCDO8,&typo=1</a><br>
<br>
I would appreciate your advice on the right way to record the correction. I would rather it be<br>
on the record than silently wrong, since this reference is the source of the published<br>
threshold our safety analysis is evaluated against, and I expect readers to follow it.<br>
<br>
My apologies for the error and for the late notice. I am grateful for any correction that is still<br>
possible.<br>
<br>
Best regards,<br>
<br>
Guilherme Lima<br>
Instituto de Tecnologia e Liderança, São Paulo, Brazil<br>
<br>
-- <br>
Hotstorage-chairs mailing list<br>
Hotstorage-chairs@fsl.cs.sunysb.edu<br>
<a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-chairs&c=E,1,XYTh9NCPtxxzrfazx7y_idzLHMuAnYamujTt0w3nOdlmPsmR7nT9Q6kf5S1OttGccVEoXG4sWd-uqQ7xA-b7F5NEgN4AUnOcLBnkeinfnoVlCpo9UM4,&typo=1">https://lists.fsl.cs.sunysb.edu/mailman/listinfo/hotstorage-chairs</a><br>
</div>
</span></font></div>
</body>
</html>