All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daeho Jeong <daeho43@gmail.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
	Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: add symbolic link to kobject in sysfs
Date: Fri, 3 Jul 2020 11:46:42 +0900	[thread overview]
Message-ID: <CACOAw_y23emnXdmbUJT_QDdF42EGJ9p4-ZuC9caJBGTpLWbR=g@mail.gmail.com> (raw)
In-Reply-To: <ee97fa6e-33df-04f9-ec37-6b7d7b495acb@huawei.com>

Got it.

Thanks~

2020년 7월 3일 (금) 오전 11:02, Chao Yu <yuchao0@huawei.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.
> > .
> >

WARNING: multiple messages have this Message-ID (diff)
From: Daeho Jeong <daeho43@gmail.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: Daeho Jeong <daehojeong@google.com>,
	kernel-team@android.com, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: add symbolic link to kobject in sysfs
Date: Fri, 3 Jul 2020 11:46:42 +0900	[thread overview]
Message-ID: <CACOAw_y23emnXdmbUJT_QDdF42EGJ9p4-ZuC9caJBGTpLWbR=g@mail.gmail.com> (raw)
In-Reply-To: <ee97fa6e-33df-04f9-ec37-6b7d7b495acb@huawei.com>

Got it.

Thanks~

2020년 7월 3일 (금) 오전 11:02, Chao Yu <yuchao0@huawei.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.
> > .
> >


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2020-07-03  2:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  0:56 [PATCH] f2fs: add symbolic link to kobject in sysfs Daeho Jeong
2020-06-30  0:56 ` [f2fs-dev] " Daeho Jeong
2020-07-01  6:36 ` Chao Yu
2020-07-01  6:36   ` Chao Yu
2020-07-01  7:04   ` Daeho Jeong
2020-07-01  7:04     ` Daeho Jeong
2020-07-01  7:15     ` Chao Yu
2020-07-01  7:15       ` Chao Yu
2020-07-01 12:12       ` Daeho Jeong
2020-07-01 12:12         ` Daeho Jeong
2020-07-03  2:02         ` Chao Yu
2020-07-03  2:02           ` Chao Yu
2020-07-03  2:46           ` Daeho Jeong [this message]
2020-07-03  2:46             ` Daeho Jeong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACOAw_y23emnXdmbUJT_QDdF42EGJ9p4-ZuC9caJBGTpLWbR=g@mail.gmail.com' \
    --to=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.