lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fa2b0f11-d8bc-4d7c-b6dd-435eeacd6d37@gmail.com>
Date: Tue, 26 Nov 2024 10:49:03 +0530
From: Suraj Sonawane <surajsonawane0215@...il.com>
To: Bart Van Assche <bvanassche@....org>, dgilbert@...erlog.com
Cc: James.Bottomley@...senPartnership.com, martin.petersen@...cle.com,
 linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
 syzbot+7efb5850a17ba6ce098b@...kaller.appspotmail.com
Subject: Re: [PATCH] scsi: sg: fix slab-use-after-free Read in sg_release

On 11/25/24 22:33, Bart Van Assche wrote:
> On 11/25/24 6:30 AM, Suraj Sonawane wrote:
>> Hello!
> 
> Which person are you addressing with this email?
> 
I apologize for not clarifying earlier—my email was intended for 
everyone who might be reviewing the patch.

>> I wanted to follow up on the patch I submitted. I was wondering if you 
>> had a chance to review it and if there are any comments or feedback.
> 
> Sending a ping after 5 days is too quick. I think that you should wait
> at least a week before sending a ping.
> 

Thank you for pointing out that sending a follow-up after five days 
might be too soon. I truly appreciate your guidance on this. The reason 
for my follow-up is that, as a mentee in the Linux Kernel Bug Fixing 
Program, I need to include updates on my contributions in my progress 
report. I’ll make sure to wait at least a week before sending any future 
follow-ups.

> Bart.
> 



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ