comment
This commit is contained in:
parent
972f41efb7
commit
4144f73c18
2 changed files with 15 additions and 1 deletions
|
@ -9,6 +9,11 @@ hook or no freeze hook), it still checks if the file's write permissions
|
|||
got removed.
|
||||
|
||||
I think that, in order to support filesystems where chmod -w has no effect,
|
||||
init should skip looking at perms when there is a freeze hook. It can
|
||||
init should skip looking at write perms when there is a freeze hook. It can
|
||||
still check that freezing prevents writing to a file.
|
||||
|
||||
Hmm, init uses checkContentWritePerm to see if the write permission is
|
||||
removed. That is also used by fsck, and when ingesting a file. So even if
|
||||
it were fixed in init, those would still be problems. This really needs to
|
||||
be fixed in checkContentWritePerm.
|
||||
"""]]
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 4"""
|
||||
date="2022-02-24T17:07:19Z"
|
||||
content="""
|
||||
I think that this issue with drop freezing the content needs to be treated
|
||||
as a separate bug. There also may be a good reason for it to do it, I have
|
||||
not looked into that yet.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue