>
> Link: https://www.openwall.com/lists/oss-security/2023/09/08/4
> Cc: Greg Kroah-Hartman
> Cc: Kees Cook
> Cc: Solar Designer
> Cc: Vegard Nossum
> Signed-off-by: Willy Tarreau
With my distro hat on:
Acked-by: Jiri Kosina
Thanks a lot,
--
Jiri Kosina
SUSE Labs
s.
Thanks again,
--
Jiri Kosina
SUSE Labs
ention, it should be spelled out loud and clear.
Thanks,
--
Jiri Kosina
SUSE Labs
ication, we
> can gladly use the help.
Thanks, but no, thanks, I want to stay away from the CVE tragedy as far as
possible :)
--
Jiri Kosina
SUSE Labs
h fantasy,
you'll come up with a scenario where this will cause some real issues to
some living human.
That's not what CVE is about at all, at least in my understaing.
--
Jiri Kosina
SUSE Labs
read: Linux distros) (*) ... or is it?
(*) just looking at how much those not-basing-on-stable distros are
contributing to mainline
Thanks,
--
Jiri Kosina
SUSE Labs
ctive and creative (upstream) work on hold in order to have
enough resources to sort out the havoc that LTS team is apparently going
to create by DoSing the world with a truckload of irrelevant CVEs.
--
Jiri Kosina
SUSE Labs
effort is magically solving for everybody out there either
using Linux, or producing something around/on-top-of Linux. And I still
don't get it.
Thanks,
--
Jiri Kosina
SUSE Labs
but there is a much more up-to-date
version of that document (especially when it comes to vendor contacts),
which I sent around on Thu, 2 May 2019 20:23:48 +0200 (CEST) already.
Please find it below.
From: Jiri Kosina
Subject: [PATCH] Documentation/admin-guide: Embargoed hardware secur
On Sun, 4 Aug 2019, Jiri Kosina wrote:
> On Thu, 25 Jul 2019, Greg Kroah-Hartman wrote:
>
> > To address the requirements of embargoed hardware issues, like Meltdown,
> > Spectre, L1TF, etc. it is necessary to define and document a process for
> > handling embargoed
> in klp_reverse_transition() described by Petr, or might be somewhere
> else. I'll look into it.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
7;t set ABS_MT_ORIENTATION in ABS_DG_HEIGHT when it is already
> set by ABS_DG_AZIMUTH.
> v4 -> v5:
>- Improve multi-touch-protocol.rst documentation.
>
> Signed-off-by: Wei-Ning Huang
> Signed-off-by: Wei-Ning Huang
> Reviewed-by: Dmitry Torokhov
This is now queued
On Fri, 2 Mar 2018, Aishwarya Pant wrote:
> Descriptions have been collected from git commit logs.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majo
On Fri, 2 Mar 2018, Aishwarya Pant wrote:
> Add sysfs documentation for N-Trig touchscreens under Documentation/ABI.
> Descriptions have been collected from code comments.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-
tches) and also your mail client damaged the
diff so that it can't be applied (please see some hints in
Documentation/email-clients.txt).
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.ker
#ifdef MODULE
#define __MODULE_INFO(tag, name, info) \
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ne of the ususal sizes.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
s / Martin's Ack before
merging this.
Hence, let me piggy back on this ping to Rusty, and let me ping Heiko and
Martin as well (adding to CC explicitly to make sure this doesn't get lost
in general noise).
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the
I was waiting a bit whether there would be any discussion regarding the
new relocation flag and symbol section index added to elf, but given the
fact that noone objected and that we are using the OS-specific range
anyway, I don't expect this to be an issue.
Thanks everybody,
--
Jiri Kosi
I've applied the whole series (with the small Documentation tweak
suggested by Petr) to livepatching.git#for-4.9/klp-paravirt-alternatives
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a me
wonder why even the original code is not racy for example against
> module_get_kallsym. It is called without the mutex. This code sets the
> number of entries before the pointer to the entries.
>
> Note that the module is in the list even in the UNFORMED state.
module_kallsyms_on_each_symbol() gi
somewhere earlier in this thread.
The most important (from the code quality POV) thing is -- is there a
person that understands the patch enough to be able to answer questions
(coming from some other human -- most likely reviewer/maintainer)?
That's not something that'd be reflected in DCO, but it's very important
fact for the maintainer's decision process.
--
Jiri Kosina
SUSE Labs
proxying the responsibility
(if he/she decides to do so), with all the consequences (again, not
talking legal here at all).
Thanks,
--
Jiri Kosina
SUSE Labs
before sending your patch".
> >
> > 3. No tool-generated patches without prior maintainer approval.
>
> This sounds good, with a default on red. Which would enforce the opt-in
> part.
I strongly believe that at least a distinction between 'static tools' and
'LLM-based tools' needs to be introduced here.
Thanks,
--
Jiri Kosina
SUSE Labs
24 matches
Mail list logo
