From: Willy Tarreau <w@1wt.eu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
keyrings@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Salvatore Bonaccorso <carnil@debian.org>,
David Woodhouse <dwmw2@infradead.org>,
David Howells <dhowells@redhat.com>,
Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [Linux v5.17.9] -Wdeprecated-declarations warnings with LLVM-14 and OpenSSL v3.0.x
Date: Thu, 9 Jun 2022 21:23:08 +0200 [thread overview]
Message-ID: <20220609192308.GB10732@1wt.eu> (raw)
In-Reply-To: <CA+icZUUma1B8KFWF-ed9sjXH4QpCRZ+B2pON3uAFkTUs77tMzw@mail.gmail.com>
On Thu, Jun 09, 2022 at 09:19:20PM +0200, Sedat Dilek wrote:
> On Thu, Jun 9, 2022 at 9:05 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Thu, Jun 9, 2022 at 11:41 AM Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > >
> > > Why go back and forth... do it like Alexander the Great and the Gordian knot.
> > >
> > > Sword - Swash - Done.
> > >
> > > commit 6bfb56e93bcef41859c2d5ab234ffd80b691be35
> > > "cert host tools: Stop complaining about deprecated OpenSSL functions"
> >
> > Well, it's not like that is the *right* fix.
> >
> > But I think for now, the answer is "leave it like that until we can
> > just get rid of the ENGINE API entirely".
> >
> > I absolutely detest the "deprecation" warnings. We used to do that in
> > the kernel too, and it was a complete disaster. The warnings are very
> > noisy, and nobody ever cares about them, so it's simply not worth it.
> >
> > So we deprecated "__deprecated" in the kernel itself:
> >
> > 771c035372a0 deprecate the '__deprecated' attribute warnings
> > entirely and for good
> >
> > and I don't think we should care about it when it comes to OpenSSL either.
> >
> > Eventually, that deprecated interface will go away entirely, and by
> > then we hopefully don't care about really old openssl implementations
> > and will have gotten rid of the uses.
> >
> > But for now, I think putting our head in the sand is actually the
> > _better_ model rather than fighting some battle over old vs new
> > libraries.
> >
> > Because sometimes, if you ignore a problem, it really does just go away.
> >
>
> To be honest: I like your approach, Linus.
> Very pragma-tic.
> That's why you use pragma's in your patch :-).
>
> I invested too much of my lifetime in making things work "correctly".
> And yes, it's post-rc1...
>
> Most of the apps in the Debian world passed the OpenSSL-v3 transition.
IIRC you can also disable the deprecation warnings by defining the
OPENSSL_SUPPRESS_DEPRECATED macro. It doesn't require to change the
compiler's options and allows us to put our head in the sand.
Willy
next prev parent reply other threads:[~2022-06-09 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 9:55 Sedat Dilek
2022-05-19 10:01 ` Sedat Dilek
2022-05-24 19:13 ` Sedat Dilek
2022-05-27 7:47 ` Sedat Dilek
2022-05-27 16:05 ` Sedat Dilek
2022-06-09 18:40 ` Sedat Dilek
2022-06-09 19:04 ` Linus Torvalds
2022-06-09 19:19 ` Sedat Dilek
2022-06-09 19:23 ` Willy Tarreau [this message]
2022-06-09 19:25 ` Linus Torvalds
2022-06-09 19:31 ` Sedat Dilek
2022-06-22 18:37 ` Andres Freund
2022-08-06 7:42 ` Sedat Dilek
2022-06-09 19:32 ` Willy Tarreau
2022-06-09 19:34 ` Linus Torvalds
2022-06-09 19:41 ` Sedat Dilek
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=20220609192308.GB10732@1wt.eu \
--to=w@1wt.eu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=carnil@debian.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keescook@chromium.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=tasmiya@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®