Got it. Thanks~
2020년 7월 3일 (금) 오전 11:02, Chao Yu <[email protected]>님이 작성: > > 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. > > . > > _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
