Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process

2024-02-15 Thread Oleksandr Natalenko
ally security issues are identified by the developers responsible > > > +for CVE number assignments and have CVE numbers automatically assigned > > > +to them. These assignments are published on the linux-cve-announce > > > +mailing list as announcements on a frequent basis. > > > + > > > +Note, due to the layer at which the Linux kernel is in a system, almost > > > +any bug might be exploitable to compromise the security of the kernel, > > > > Just a nit: but I would say: a kernel bug is compromising the > > "security of the system"; the kernel bug just happens to allow anyone > > to run any code on their hardware... in some systems that is a > > security issue, but in my previous MSDOS system that was the default > > behaviour ;) > > Good change, made, thanks! > > greg k-h > > -- Oleksandr Natalenko (post-factum) signature.asc Description: This is a digitally signed message part.

Re: [PATCH] docs: admin-guide: fix printk_ratelimit explanation

2019-10-09 Thread Oleksandr Natalenko
Hi. On Wed, Oct 02, 2019 at 01:46:10PM +0200, Oleksandr Natalenko wrote: > The printk_ratelimit value accepts seconds, not jiffies (though it is > converted into jiffies internally). Update documentation to reflect > this. > > Also, remove the statement about allowing 1 messa

[PATCH] docs: admin-guide: fix printk_ratelimit explanation

2019-10-02 Thread Oleksandr Natalenko
, mention default value for printk_ratelimit_burst too. Signed-off-by: Oleksandr Natalenko --- Documentation/admin-guide/sysctl/kernel.rst | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst

Re: [PATCH 0/8] docs: Fixes for recent versions of Sphinx

2019-05-23 Thread Oleksandr Natalenko
On Thu, May 23, 2019 at 07:45:45AM -0300, Mauro Carvalho Chehab wrote: > Em Thu, 23 May 2019 11:39:44 +0200 > Oleksandr Natalenko escreveu: > > > Hi. > > > > On Wed, May 22, 2019 at 02:50:26PM -0600, Jonathan Corbet wrote: > > > The Sphinx folks deprecate

Re: [PATCH 0/8] docs: Fixes for recent versions of Sphinx

2019-05-23 Thread Oleksandr Natalenko
On Thu, May 23, 2019 at 01:13:23PM +0300, Jani Nikula wrote: > On Thu, 23 May 2019, Oleksandr Natalenko wrote: > > Thanks for the efforts. I've run this on top of Linus' tree, and the > > only sphinx-related deprecation warning I've spotted is this one: > &g

Re: [PATCH 0/8] docs: Fixes for recent versions of Sphinx

2019-05-23 Thread Oleksandr Natalenko
x/cdomain.py:51: RemovedInSphinx30Warning: app.override_domain() is deprecated. Use app.add_domain() with override option instead. app.override_domain(CDomain) Otherwise, it builds. -- Best regards, Oleksandr Natalenko (post-factum) Senior Software Maintenance Engineer

Re: [PATCH RFC 0/2] docs: Deal with some Sphinx deprecation warnings

2019-05-22 Thread Oleksandr Natalenko
On Wed, May 22, 2019 at 11:43:54AM +0200, Oleksandr Natalenko wrote: > On Tue, May 21, 2019 at 03:17:12PM -0600, Jonathan Corbet wrote: > > The Sphinx folks are deprecating some interfaces in the upcoming 2.0 > > release; one immediate result of that is a bunch of warnings that s

Re: [PATCH RFC 0/2] docs: Deal with some Sphinx deprecation warnings

2019-05-22 Thread Oleksandr Natalenko
-) > create mode 100644 Documentation/sphinx/kernellog.py > > -- > 2.21.0 > -- Best regards, Oleksandr Natalenko (post-factum) Senior Software Maintenance Engineer

Re: [PATCH 00/12] unify the interface of the proportional-share policy in blkio/io

2018-11-15 Thread Oleksandr Natalenko
block make [1] git://git.kernel.dk/linux-block [1] Checking this: http://git.kernel.dk/cgit/linux-block/tree/include/net/xfrm.h?h=for-4.21/block#n1465 and `git blame`, I don't see any `spruct` there. Is your storage OK? Or, maybe, that was some accidental edit? -- Oleksandr Natalenko (post-factum)

Re: [PATCH V3] KSM: allow dedup all tasks memory

2018-11-13 Thread Oleksandr Natalenko
pe* this will be enough to prevent task_struct from disappearing in the meantime. Someone, correct me if I'm wrong. -- Oleksandr Natalenko (post-factum)

Re: [PATCH V3] KSM: allow dedup all tasks memory

2018-11-13 Thread Oleksandr Natalenko
read_unlock(&tasklist_lock); + + schedule_timeout_interruptible( + msecs_to_jiffies(ksm_thread_seeker_sleep_millisecs)); + } + return 0; +} …snip… -- Oleksandr Natalenko (post-factum)

Re: [PATCH V3] KSM: allow dedup all tasks memory

2018-11-13 Thread Oleksandr Natalenko
state that they're not using memory deduplication. I tend to disagree here. Based on both what my company does and what UKSM users do, memory dedup is a desired option (note "option" word here, not the default choice). Thanks. -- Oleksandr Natalenko (post-factum)

Re: [PATCH V3] KSM: allow dedup all tasks memory

2018-11-13 Thread Oleksandr Natalenko
you compared these results with UKSM [1]? Thanks. -- Oleksandr Natalenko (post-factum) [1] https://github.com/dolohow/uksm

Re: [PATCH 00/12] unify the interface of the proportional-share policy in blkio/io

2018-11-12 Thread Oleksandr Natalenko
On 12.11.2018 11:00, Oleksandr Natalenko wrote: I thought all the legacy stuff including CFS et al. is going to be removed in v4.21 completely… Paolo, [1] and [2]. [1] http://git.kernel.dk/cgit/linux-block/log/?h=for-4.21/block [2] http://git.kernel.dk/cgit/linux-block/commit/?h=for-4.21

Re: [PATCH 00/12] unify the interface of the proportional-share policy in blkio/io

2018-11-12 Thread Oleksandr Natalenko
ernel/cgroup/cgroup.c | 262 +--- 12 files changed, 483 insertions(+), 170 deletions(-) -- 2.16.1 I thought all the legacy stuff including CFS et al. is going to be removed in v4.21 completely… -- Oleksandr Natalenko (post-factum)