From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] env: Fix warning when forcing environment without ENV_ACCESS_IGNORE_FORCE
Date: Fri, 29 Jan 2021 00:05:00 +0100 [thread overview]
Message-ID: <d6041ed7-a081-695d-d77f-380642d53fe7@denx.de> (raw)
In-Reply-To: <CANh8Qzz-RGkROWRGDs_fAPStfuL-hCn_=hpKEW5PYOZb0sZpuA@mail.gmail.com>
On 1/28/21 8:37 PM, Fuzzey, Martin wrote:
> Hi Marek,
Hi,
> On Thu, 28 Jan 2021 at 20:07, Marek Vasut <marex@denx.de> wrote:
>>
>> Based on env/Kconfig description of this option:
>>
>> config ENV_ACCESS_IGNORE_FORCE
>> bool "Block forced environment operations"
>> default n
>> help
>> If defined, don't allow the -f switch to env set override
>> variable
>> access flags.
>>
>> I would think the code should look like this:
>>
>> #ifdef CONFIG_ENV_ACCESS_IGNORE_FORCE
>> if (flag & H_FORCE) {
>> printf("## Error: Can't force access to \"%s\"\n", name);
>> return 1;
>> }
>> #else
>> if (flag & H_FORCE)
>> return 0;
>> #endif
>
> I don't think that is right.
>
> If you do that force update will be refused when
> CONFIG_ENV_ACCESS_IGNORE_FORCE, regardless if the access would be
> valid without the force
That's how I understand the option was intended to work, based on the
Kconfig help text.
> The kconfig options says don't allow the -f switch to OVERRIDE
> variable access flags, not "don't allow the -f switch to be used"
I suspect the help text needs clarification then.
next prev parent reply other threads:[~2021-01-28 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 10:27 [PATCH] env: Fix warning when forcing environment without ENV_ACCESS_IGNORE_FORCE Martin Fuzzey
2021-01-15 18:43 ` Tom Rini
2021-01-28 16:25 ` Tom Rini
2021-01-28 9:11 ` Heinrich Schuchardt
2021-01-28 18:59 ` Marek Vasut
2021-01-28 19:07 ` Marek Vasut
2021-01-28 19:26 ` Tom Rini
2021-01-28 23:03 ` Marek Vasut
2021-02-01 19:31 ` Tom Rini
2021-02-03 16:39 ` Marek Vasut
2021-01-28 19:37 ` Fuzzey, Martin
2021-01-28 23:05 ` Marek Vasut [this message]
2021-01-29 7:42 ` Fuzzey, Martin
2021-01-29 11:16 ` Marek Vasut
2021-04-18 12:45 ` Tom Rini
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=d6041ed7-a081-695d-d77f-380642d53fe7@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.