From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 202637] Chmod'ed directory permission is not persisted with fsync
Date: Mon, 25 Feb 2019 19:30:47 +0000 [thread overview]
Message-ID: <bug-202637-202145-IflBiWaVYH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202637-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202637
--- Comment #2 from Seulbae Kim (seulbae@gatech.edu) ---
Thank you for quick response Chao Yu!
I tested your patch by applying it on kernel v5.0.0-rc7, and confirmed that the
reported bug is fixed.
(In reply to Chao Yu from comment #1)
> Seulbae, thanks for the report.
>
> I've written a patch for that, could you please check it?
>
> [PATCH] f2fs: fix to dirty inode for i_mode recovery
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-02-25 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 3:05 [Bug 202637] New: Chmod'ed directory permission is not persisted with fsync bugzilla-daemon
2019-02-24 3:12 ` [Bug 202637] " bugzilla-daemon
2019-02-25 19:30 ` bugzilla-daemon [this message]
2019-02-26 8:40 ` bugzilla-daemon
2019-03-16 8:03 ` bugzilla-daemon
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=bug-202637-202145-IflBiWaVYH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).