* RE: [PATCH] f2fs:Fix locking requirements in the function recover_dentry
[not found] <1441474037-6931-1-git-send-email-xerofoify@gmail.com>
@ 2015-09-06 9:41 ` Chao Yu
0 siblings, 0 replies; only message in thread
From: Chao Yu @ 2015-09-06 9:41 UTC (permalink / raw)
To: 'Nicholas Krause', jaegeuk
Cc: cm224.lee, linux-f2fs-devel, linux-kernel
> -----Original Message-----
> From: Nicholas Krause [mailto:xerofoify@gmail.com]
> Sent: Sunday, September 06, 2015 1:27 AM
> To: jaegeuk@kernel.org
> Cc: cm224.lee@samsung.com; chao2.yu@samsung.com; linux-f2fs-devel@lists.sourceforge.net;
> linux-kernel@vger.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,
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-09-06 9:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1441474037-6931-1-git-send-email-xerofoify@gmail.com>
2015-09-06 9:41 ` [PATCH] f2fs:Fix locking requirements in the function recover_dentry Chao Yu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome