All of lore.kernel.org
 help / color / mirror / Atom feed
From: youling 257 <youling257@gmail.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Arvind Sankar <nivedita@alum.mit.edu>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH] early init: open /dev/console with O_LARGEFILE
Date: Wed, 1 Jan 2020 21:27:27 +0800	[thread overview]
Message-ID: <CAOzgRdZ0eBNKAP_T8r=MF35WUtUMn07-14OwA+AXACyY=r5hqA@mail.gmail.com> (raw)
In-Reply-To: <20200101104313.GA666771@light.dominikbrodowski.net>

Unfortunately, test this patch still no help, has system/bin/sh warning.

2020-01-01 18:43 GMT+08:00, Dominik Brodowski <linux@dominikbrodowski.net>:
> @youling 257: could you test the attached patch, please?
>
> Thanks,
> 	Dominik
>
> On Tue, Dec 31, 2019 at 07:30:19PM -0500, Arvind Sankar wrote:
>> On Tue, Dec 31, 2019 at 04:02:26PM +0100, Dominik Brodowski wrote:
>> > If force_o_largefile() is true, /dev/console used to be opened
>> > with O_LARGEFILE. Retain that behaviour.
>> >
>>
>> One other thing that used to happen is fsnotify_open() -- I don't know
>> how that might affect this, but it seems like the only thing left that's
>> different.
>
> Suggested-by: Arvind Sankar <nivedita@alum.mit.edu>
> Signed-off-by: Dominik Brodowski <linux@dominikbrodowski.net>
>
> diff --git a/init/main.c b/init/main.c
> index d12777775cb0..3f4163046200 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -94,6 +94,7 @@
>  #include <linux/jump_label.h>
>  #include <linux/mem_encrypt.h>
>  #include <linux/file.h>
> +#include <linux/fsnotify.h>
>
>  #include <asm/io.h>
>  #include <asm/bugs.h>
> @@ -1166,6 +1167,7 @@ void console_on_rootfs(void)
>  			  O_RDWR | (force_o_largefile() ? O_LARGEFILE : 0), 0);
>  	if (IS_ERR(file))
>  		goto err_out;
> +	fsnotify_open(file);
>
>  	/* create stdin/stdout/stderr, this should never fail */
>  	for (i = 0; i < 3; i++) {
>

  reply	other threads:[~2020-01-01 13:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-31 15:02 [PATCH] early init: open /dev/console with O_LARGEFILE Dominik Brodowski
2019-12-31 15:55 ` youling 257
2020-01-01  0:30 ` Arvind Sankar
2020-01-01 10:43   ` Dominik Brodowski
2020-01-01 13:27     ` youling 257 [this message]
2020-01-01 17:24       ` Dominik Brodowski
2020-01-01 17:59       ` Arvind Sankar
2020-01-01 18:42         ` Dominik Brodowski
2020-01-01 18:49           ` youling 257
2020-01-01 18:32   ` Arvind Sankar
2020-01-01 21:39     ` Linus Torvalds
2020-01-01 22:50       ` Arvind Sankar
2020-01-01 23:01         ` Linus Torvalds
2020-01-01 23:08           ` Arvind Sankar
2020-01-02  3:09       ` youling 257
2020-01-02  4:00         ` Linus Torvalds
2020-01-02  4:10           ` Arvind Sankar
2020-01-02 17:53       ` Dominik Brodowski

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='CAOzgRdZ0eBNKAP_T8r=MF35WUtUMn07-14OwA+AXACyY=r5hqA@mail.gmail.com' \
    --to=youling257@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=nivedita@alum.mit.edu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.