From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, david.laight@aculab.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
tanyuan@tinylab.org, thomas@t-8ch.de
Subject: Re: [PATCH v6 2/2] tools/nolibc: fix up size inflate regression
Date: Mon, 14 Aug 2023 09:25:52 +0200 [thread overview]
Message-ID: <20230814072552.GD14322@1wt.eu> (raw)
In-Reply-To: <20230813133944.19604-1-falcon@tinylab.org>
On Sun, Aug 13, 2023 at 09:39:44PM +0800, Zhangjin Wu wrote:
> > Let's just roll brk(), mmap() and sbrk() to their original, working,
> > definition:
> >
> > static __attribute__((unused))
> > void *mmap(void *addr, size_t length, int prot, int flags, int fd, off_t offset)
> > {
> > void *ret = sys_mmap(addr, length, prot, flags, fd, offset);
> >
> > if ((unsigned long)ret >= -MAX_ERRNO) {
> > SET_ERRNO(-(long)ret);
> > ret = MAP_FAILED;
> > }
> > return ret;
> > }
> >
>
> Agree, only left a suggestion here [2] about whether we can apply the 2nd patch
> instead of rolling them back, let's discuss it in [2] thread.
(...)
> [2]: https://lore.kernel.org/lkml/20230813132620.19411-1-falcon@tinylab.org/
I'm sorry but I can't find this "suggestion" in this yet-another-super-
long-description-of-another-idea-of-redesign. In addition it's extremely
painful to constantly have to go through web links to follow a single
conversation. Mail works in threads for a reason. When the same discussion
is handled in many parallel threads it becomes impossible to keep it
focused on a specific topic. This is also why you should stop systematically
responding to a message with yet another redesign suggestion, this is super
hard to follow and it literally takes me several hours a week! And at the
end we've not addressed the initial problem but discussed plenty of other
things.
Thanks,
Willy
next prev parent reply other threads:[~2023-08-14 7:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 21:49 [PATCH v6 0/2] tools/nolibc: fix up size inflat regression Zhangjin Wu
2023-08-11 21:50 ` [PATCH v6 1/2] tools/nolibc: let sys_brk, sys_mmap and sys_mmap2 return long Zhangjin Wu
2023-08-11 21:51 ` [PATCH v6 2/2] tools/nolibc: fix up size inflate regression Zhangjin Wu
2023-08-13 9:00 ` Willy Tarreau
2023-08-13 13:39 ` Zhangjin Wu
2023-08-14 7:25 ` Willy Tarreau [this message]
2023-08-15 12:17 ` Willy Tarreau
2023-08-15 16:34 ` Zhangjin Wu
2023-08-13 9:08 ` [PATCH v6 0/2] tools/nolibc: fix up size inflat regression Willy Tarreau
2023-08-13 13:56 ` Zhangjin Wu
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=20230814072552.GD14322@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=david.laight@aculab.com \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tanyuan@tinylab.org \
--cc=thomas@t-8ch.de \
/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