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
| ||
|
Date: Fri, 3 Jul 2020 11:46:42 +0900 From: Daeho Jeong <daeho43@...il.com> To: Chao Yu <yuchao0@...wei.com> Cc: linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net, kernel-team@...roid.com, Daeho Jeong <daehojeong@...gle.com> Subject: Re: [f2fs-dev] [PATCH] f2fs: add symbolic link to kobject in sysfs Got it. Thanks~ 2020년 7월 3일 (금) 오전 11:02, Chao Yu <yuchao0@...wei.com>님이 작성: > > On 2020/7/1 20:12, Daeho Jeong wrote: > >> On 2020/7/1 15:04, Daeho Jeong wrote: > >>> Actually, I want to keep the mount number remaining to the same > >>> number, even if it's re-mounted. > >> > >> Then once there is f2fs umounter, the order will be incorrect... > > > > Actually, we prepared this patch for a strictly controlled system like > > Android to easily access the sysfs node for a specific partition like > > userdata partition using a specific number. > > I'm not against Android defined interfaces, just be confused about the > behavior that does not fully documented (at least, we should add this > into f2fs doc, and specify this is android specified interface), something > like once one mount point was umounted, that sequential number @x in > 'mount_@x" could be reused by later newly mounted point, it breaks the > description: "in the order of mounting filesystem". > > > In this system, we don't worry about another unexpected f2fs umounter > > interfering in between unmounting and mounting a partition. > > > > When we are under the condition that we can keep track of how many > > times the userdata partition has been re-mounted, we might as well use > > the original partition name like "/sys/fs/f2fs/dm-9". > > This is for when we couldn't do that. > > . > >
Powered by blists - more mailing lists