From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] vfs: introduce UMOUNT_WAIT which waits for umount completion
Date: Wed, 13 Sep 2017 18:10:48 -0700 [thread overview]
Message-ID: <20170914011048.GA47448@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <20170913234437.GO5426@ZenIV.linux.org.uk>
On 09/14, Al Viro wrote:
> On Wed, Sep 13, 2017 at 04:31:16PM -0700, Jaegeuk Kim wrote:
> > Hi Al,
> >
> > On 09/14, Al Viro wrote:
> > > On Wed, Sep 13, 2017 at 01:09:41PM -0700, Jaegeuk Kim wrote:
> > > > + if (!retval && (flags & UMOUNT_WAIT)) {
> > > > + if (likely(!(current->flags & PF_KTHREAD)))
> > > > + task_work_run();
> > >
> > > This is complete crap. The same damn thing will be done by
> > > caller of sys_umount() pretty much immediately afterwards.
> > > I'm not sure what it is that you are trying to paper over,
> > > but this is just plain wrong.
> >
> > Okay.
> >
> > > What _is_ the semantics of UMOUNT_WAIT? What does it guarantee,
> > > and what would be supplying it to umount(2)?
> >
> > When android tries to reboot the system, it calls umount(2) without any flag.
> > Then, mntput_no_expire() will add delayed_mntput_work() which finally does
> > cleanup_mnt() later. In the mean time, android proceeded to shutdown all
> > the UFS devices.
>
> Why has task_work_add() failed? Or is that umount(2) issued by a kernel thread?
Android triggers umount(2) by init process, which is definitely not a kernel
thread. But, we've seen some kernel panics which say umount(2) was succeeded,
but ext4 triggered a kernel panic due to EIO after then like below. I'm also
not sure task_work_run() would be also safe enoughly. May I ask where I can
find sys_umount() calls task_work_run()?
[254012.860565] c4 12426 [<ffffff909b6a7ebc>] panic+0x184/0x37c
[254012.860589] c4 12426 [<ffffff909b88e724>] __ext4_abort+0x198/0x19c
[254012.860606] c4 12426 [<ffffff909b897468>] ext4_put_super+0x80/0x2b4
[254012.860629] c4 12426 [<ffffff909b7e7274>] generic_shutdown_super+0x68/0xd0
[254012.860646] c4 12426 [<ffffff909b7e87fc>] kill_block_super+0x1c/0x5c
[254012.860663] c4 12426 [<ffffff909b7e70dc>] deactivate_locked_super+0x5c/0xc0
[254012.860679] c4 12426 [<ffffff909b7e71a8>] deactivate_super+0x68/0x74
[254012.860696] c4 12426 [<ffffff909b80a25c>] cleanup_mnt+0xb0/0x12c
[254012.860712] c4 12426 [<ffffff909b80a310>] delayed_mntput+0x38/0x4c
[254012.860737] c4 12426 [<ffffff909b6c6524>] process_one_work+0x1e0/0x490
[254012.860753] c4 12426 [<ffffff909b6c6094>] worker_thread+0x314/0x494
[254012.860771] c4 12426 [<ffffff909b6cb35c>] kthread+0xdc/0xec
[254012.860790] c4 12426 [<ffffff909b683860>] ret_from_fork+0x10/0x30
next prev parent reply other threads:[~2017-09-14 1:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 20:09 Jaegeuk Kim
2017-09-13 23:04 ` Al Viro
2017-09-13 23:31 ` Jaegeuk Kim
2017-09-13 23:44 ` Al Viro
2017-09-14 1:10 ` Jaegeuk Kim [this message]
2017-09-14 1:30 ` Al Viro
2017-09-14 18:37 ` Al Viro
2017-09-14 19:14 ` Jaegeuk Kim
2017-09-15 0:19 ` Jaegeuk Kim
2017-09-15 2:06 ` Al Viro
2017-09-15 3:45 ` Jaegeuk Kim
2017-09-15 4:21 ` Al Viro
2017-09-15 18:44 ` Jaegeuk Kim
2017-09-15 22:12 ` Theodore Ts'o
2017-09-15 23:29 ` Jaegeuk Kim
2017-09-15 23:43 ` Al Viro
2017-09-19 15:55 ` Jaegeuk Kim
2017-09-16 7:11 ` Amir Goldstein
2017-09-20 17:38 ` [PATCH v2] " Jaegeuk Kim
2017-09-20 18:38 ` Al Viro
2017-09-21 0:34 ` Jaegeuk Kim
2017-09-21 2:42 ` Al Viro
2017-09-21 5:02 ` Jaegeuk Kim
2017-09-21 14:48 ` Theodore Ts'o
2017-09-21 17:16 ` Jaegeuk Kim
2017-09-21 18:20 ` [PATCH v3] vfs: introduce UMOUNT_WAIT to wait for delayed_fput/mntput completion Jaegeuk Kim
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=20170914011048.GA47448@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®