KernelCI discussions
 help / color / mirror / Atom feed
From: Naveen Nathan <naveen@lastninja.net>
To: info@kernelci.org
Subject: Who should I talk to about making kernel changes that could potential break CI
Date: Wed, 26 Jun 2019 08:21:24 +1000	[thread overview]
Message-ID: <20190625222124.GA79586@armakuni.lastninja.net> (raw)

Hi,

A few months ago I submitted a patch [1] to make /dev/urandom block until
sufficient entropy is gathered; this is blocked by a kernel config
option CONFIG_SECURE_URANDOM=[yn].

If set, this will break systemd systems.

If set, this will probably break Kernel CI (afaik tests are run on
Debian which use systemd) - specifically when randconfig is used
and the config option is set to y.

There is no longer a 'CONFIG_EXPERIMENTAL', to depend/block on, so
I cannot rely on that going forward.

I was hoping to work with the Kernel CI peeps to see if we can prepare
the Kernel CI system to support this config option.

Thanks,
Naveen

[1]: https://lore.kernel.org/patchwork/patch/1079511/

             reply	other threads:[~2019-06-25 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 22:21 Naveen Nathan [this message]
2019-06-26 11:50 ` Who should I talk to about making kernel changes that could potential break CI Mark Brown

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=20190625222124.GA79586@armakuni.lastninja.net \
    --to=naveen@lastninja.net \
    --cc=info@kernelci.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