* [PATCH 1/2] f3: safer fixed buffer size for alternate F3_NS
2023-07-26 12:45 6% [PATCH 0/2] fuse3 branch updates Eric Wong
@ 2023-07-26 12:45 7% ` Eric Wong
0 siblings, 0 replies; 2+ results
From: Eric Wong @ 2023-07-26 12:45 UTC (permalink / raw)
To: meta
This accounts for longer F3_NS values if we need them.
---
lib/PublicInbox/f3.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/PublicInbox/f3.h b/lib/PublicInbox/f3.h
index 3ac3f575..4494e61b 100644
--- a/lib/PublicInbox/f3.h
+++ b/lib/PublicInbox/f3.h
@@ -1347,7 +1347,7 @@ f3_getxattr(fuse_req_t req, fuse_ino_t ino, const char *name, size_t size)
size_t rlen = sizeof(fxr);
if (ino == FUSE_ROOT_ID) { /* show f3 internal vars */
- char x[80];
+ char x[sizeof(F3_NS) + 75];
int n = INT_MAX;
if (!strcmp(name, F3_NS".entry_timeout"))
^ permalink raw reply related [relevance 7%]
* [PATCH 0/2] fuse3 branch updates
@ 2023-07-26 12:45 6% Eric Wong
2023-07-26 12:45 7% ` [PATCH 1/2] f3: safer fixed buffer size for alternate F3_NS Eric Wong
0 siblings, 1 reply; 2+ results
From: Eric Wong @ 2023-07-26 12:45 UTC (permalink / raw)
To: meta
Brain is fried from coderepo <=> inbox joins, some FUSE3 stuff
from the other project using this shim...
Patch 2/2: naming things is hard :< I think `lei' is a
suitable FS name, since `leifs' is very confusing.
The mount executable can be `lei.fuse'...
Eric Wong (2):
f3: safer fixed buffer size for alternate F3_NS
f3: define F3_NS in cflags rather than C code
lib/PublicInbox/LeiF3.pm | 5 +++--
lib/PublicInbox/f3.h | 8 +++++---
2 files changed, 8 insertions(+), 5 deletions(-)
^ permalink raw reply [relevance 6%]
Results 1-2 of 2 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2023-07-26 12:45 6% [PATCH 0/2] fuse3 branch updates Eric Wong
2023-07-26 12:45 7% ` [PATCH 1/2] f3: safer fixed buffer size for alternate F3_NS Eric Wong
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).