All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Hiromu Yakura <hiromu1996@gmail.com>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	zippel@linux-m68k.org
Subject: Re: [PATCH] Kconfig: add warning about permission of config file
Date: Tue, 24 May 2011 17:01:26 +0200	[thread overview]
Message-ID: <4DDBC846.8050402@suse.cz> (raw)
In-Reply-To: <1306247192.7501.25.camel@hiromu-MacBook>

On 24.5.2011 16:26, Hiromu Yakura wrote:
> Hello,
>
> On Fri, May 24, 2011 at 22:23, Michal Marek<mmarek@suse.cz>  wrote:
>> Arnaud's point is that your patch should not be necessary at all,
>> because kconfig already checks the return value of the fopen() call in
>> conf_write() and prints the above message if it fails. So do you have a
>> testcase where make<...>config without your patch returns without
>> error, but the configuration is not written?
> Sorry for misunderstanding.
> Indeed, make *config which use 'conf' (e.g. oldconfig, defconfig...)
> raise error.
> And only xconfig and gconfig don't write the configuration without
> error.

I see, qconf lacks a check for the return value of conf_write() in 
ConfigMainWindow::closeEvent(), gconf does check the return value, but 
only displays it in the bottom box of the main window instead of a 
message box. Neither of them return failure in the error case. These 
bugs should be indeed fixed. But I don't like the directory permission 
check, it only handles one case, but does not handle permission on the 
.config file itself with KCONFIG_OVERWRITECONFIG=1, ENOSPC and so on.

Michal

  reply	other threads:[~2011-05-24 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 16:16 [PATCH] Kconfig: add warning about permission of config file hiromu
2011-05-23 17:58 ` Arnaud Lacombe
2011-05-24 13:06   ` Hiromu Yakura
2011-05-24 13:23     ` Michal Marek
2011-05-24 14:26       ` Hiromu Yakura
2011-05-24 15:01         ` Michal Marek [this message]
2011-05-24 15:50           ` Arnaud Lacombe
2011-05-24 16:49             ` Sam Ravnborg
2011-05-24 17:38             ` Hiromu Yakura
2011-05-24 17:59               ` Arnaud Lacombe
2011-05-24 20:46                 ` Hiromu Yakura
2011-05-24 21:49                   ` Arnaud Lacombe

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=4DDBC846.8050402@suse.cz \
    --to=mmarek@suse.cz \
    --cc=hiromu1996@gmail.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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 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.