git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: chmod failure on GVFS mounted CIFS share

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 15, 2024, 22:30 UTC
Message-ID
<Z19Ymnnvt9jOixPB@tapette.crustytoothpaste.net>
In-Reply-To
<c22a7d5e-cbfe-48a9-bdf5-e73f21ac648f@psi.ch>
On 2024-12-13 at 10:32:22, Konrad Bucheli (PSI) wrote:
> My suggestion is not to silently ignore all chmod errors, only ENOTSUP for
> config.lock which basically tells that it is not a suitable location for
> that operation and thus also not required.
> Would that be acceptable?

That solves your particular problem, but the WSL situation gets EPERM[0], so it would not solve the general problem. We definitely don't want to blindly ignore EPERM in general for `config.lock` because it could indicate a real permissions problem or a race condition with other software.

[0] https://askubuntu.com/questions/1115564/wsl-ubuntu-distro-how-to-solve-operation-not-permitted-on-cloning-repository
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
Previous: Konrad Bucheli (PSI)Next: Konrad Bucheli (PSI)
Message 4 of 8 in “chmod failure on GVFS mounted CIFS share”
  1. Konrad Bucheli (PSI)Dec 12, 2024
  2. brian m. carlsonDec 13, 2024
  3. Konrad Bucheli (PSI)Dec 13, 2024
  4. brian m. carlsonDec 15, 2024
  5. Konrad Bucheli (PSI)Dec 20, 2024
  6. Junio C HamanoDec 20, 2024
  7. Konrad Bucheli (PSI)Dec 20, 2024
  8. Konrad Bucheli (PSI)Jan 10, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.