public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Petr Vorel <pvorel@suse.cz>, Avinesh Kumar <akumar@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] crypto/af_alg0[13]: update tests for additional possible errno case
Date: Tue, 5 Nov 2024 17:42:08 +0100	[thread overview]
Message-ID: <5667b9b5-c19e-4c00-8fa1-176ae7e1176d@redhat.com> (raw)
In-Reply-To: <20241105104003.GA1573194@pevik>

On 05.11.24 11:40, Petr Vorel wrote:
> Hi Cyril, Jan, David,
> 
>> kernel behaviour wrt checking invalid algorithms has changed [1] [2]
>> updating the tests to address the additional errno case.
>> Related discussion on the mailing list [3]
> 
> Looking at 57ab2160c0 ("move_pages04: remove special-casing for kernels < 4.3") [4]
> recently reverting errnos for 4.3 d539a004dd ("move_pages04: fix zero page
> status code for kernels >= 4.3") [5] please double check this already merged
> change. I still believe it's a different case thus merging this is correct.
> Also Eric is suggesting this (I should have added Suggested-by: tag for him).
> 
> Maybe we need some rules to clarify when we are ok with different errno and when not.
> 

Right.

Regarding d539a004dd, we pretty much hid kernel bugs: behaving 
differently than expected+documented.

If the kernel starts reporting a different errno it might be a bug: user 
space might not be prepared to handle that. Or it might be expected, 
because nobody really cares about the exact error code.

So if a test starts failing, it's definitely concerning and needs a 
closer look.

> I also thought there would be some rule "don't hide kernel bugs", but I can't
> find it in the docs.

That rule makes sense to me.

-- 
Cheers,

David / dhildenb


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-11-05 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04 15:33 [LTP] [PATCH] crypto/af_alg0[13]: update tests for additional possible errno case Avinesh Kumar
2024-11-04 16:12 ` Petr Vorel
2024-11-05 10:40 ` Petr Vorel
2024-11-05 16:42   ` David Hildenbrand [this message]
2024-11-05 18:05     ` Petr Vorel
2024-11-05 19:54       ` David Hildenbrand

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=5667b9b5-c19e-4c00-8fa1-176ae7e1176d@redhat.com \
    --to=david@redhat.com \
    --cc=akumar@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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