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

Re: [PATCH] fsckObjects tests: show how v2.17.1 can exploit downstream

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 31, 2018, 06:52 UTC
Message-ID
<876034fhab.fsf@evledraar.gmail.com>
In-Reply-To
<20180531055451.GD17344@sigill.intra.peff.net>
On Thu, May 31 2018, Jeff King wrote:
Show 23 quoted lines
> On Tue, May 29, 2018 at 11:59:07PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
>> > I'm not sure what testing this buys us. [...]
>>
>> Half of what I'm trying to do here is clarifying the v2.17.1 release
>> notes. The initial version Junio had & my proposed amendment on
>> git-security was:
>
> I think that's a fine goal, but I doubt that adding a test is going to
> help much. That's why I say this seems like it should be a documentation
> patch and not a test one. People are much less likely to crawl through
> our tests than they are to crawl through the documentation.
>
>> The other half, which is why I think this patch is needed, is making
>> this aspect of it clearer to future maintainers. Before I started
>> hacking on my recent fsck series[1] I didn't realize the intricacies of
>> how *.fsckObjects worked in various situations, and I think explicitly
>> calling this case out in code helps.
>
> I agree we should be testing that, but I don't think it should be tied
> into this test that is specific to one particular fsck check. Don't we
> already check the behavior of the various fsckObjects options elsewhere,
> like in t5504?

Okey, I'll turn this into some documentation in my re-rolled fetch.fsck.* series.

Previous: Jeff KingNext: Junio C Hamano
Message 6 of 10 in “fsckObjects tests: show how v2.17.1 can exploit downstream”
  1. fsckObjects tests: show how v2.17.1 can exploit downstreamÆvar Arnfjörð Bjarmason, May 29, 2018
  2. Jeff KingMay 29, 2018
  3. Ævar Arnfjörð BjarmasonMay 29, 2018
  4. Junio C HamanoMay 30, 2018
  5. Jeff KingMay 31, 2018
  6. Ævar Arnfjörð BjarmasonMay 31, 2018
  7. Junio C HamanoMay 30, 2018
  8. Jeff KingMay 31, 2018
  9. Junio C HamanoJun 1, 2018
  10. Jeff KingJun 1, 2018

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.