linux-kernel - RE: [PATCH] f2fs:Fix locking requirements in the function recover

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>] [day] [month] [year] [list]

Message-id: <009501d0e888$6b679090$4236b1b0$@samsung.com>
Date:	Sun, 06 Sep 2015 17:41:45 +0800
From:	Chao Yu <chao2.yu@...sung.com>
To:	'Nicholas Krause' <xerofoify@...il.com>, jaegeuk@...nel.org
Cc:	cm224.lee@...sung.com, linux-f2fs-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: RE: [PATCH] f2fs:Fix locking requirements in the function
 recover_dentry

> -----Original Message-----
> From: Nicholas Krause [mailto:xerofoify@...il.com]
> Sent: Sunday, September 06, 2015 1:27 AM
> To: jaegeuk@...nel.org
> Cc: cm224.lee@...sung.com; chao2.yu@...sung.com; linux-f2fs-devel@...ts.sourceforge.net;
> linux-kernel@...r.kernel.org
> Subject: [PATCH] f2fs:Fix locking requirements in the function recover_dentry
> 
> This fixes locking requirements in the function recover_dentry to
> properly lock the critical region between the labels retry and out
> with the read/write semaphone of the f2fs's superblock representation
> in order to protect against other concurrent threads of execution

The protecting is not needed, I've already relayed in last thread, please
refer to the link below:

http://www.gossamer-threads.com/lists/linux/kernel/2234556?do=post_view_threaded#2234556

Thanks,

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/