All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] fs: initialize resize_wait wait queue of init task
       [not found] <CGME20170614002719epcas5p3882aceef116f53781449010cc13f55e5@epcas5p3.samsung.com>
@ 2017-06-14  0:27 ` Daeho Jeong
  2017-06-15 11:16   ` Al Viro
  0 siblings, 1 reply; 4+ messages in thread
From: Daeho Jeong @ 2017-06-14  0:27 UTC (permalink / raw)
  To: edumazet, mguzik, viro, linux-fsdevel; +Cc: Daeho Jeong

We don't initialize resize_wait of init task now and all the kernel
threads share this uninitialized resize_wait wait queue because they
are sharing the file table of init task. Therefore, when expanding
this file table shared by the kernel threads, we encounter kernel panic
by accessing the NULL resize_wait wait queue.

Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
Tested-by: Youngjin Gil <youngjin.gil@samsung.com>
Acked-by: Eric Dumazet <edumazet@google.com>
Fixes: 8a81252b774b ("fs/file.c: don't acquire files->file_lock in
fd_install()")
---
 fs/file.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/file.c b/fs/file.c
index ad6f094f2eff..74748c32e07a 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -475,6 +475,7 @@ struct files_struct init_files = {
 		.full_fds_bits	= init_files.full_fds_bits_init,
 	},
 	.file_lock	= __SPIN_LOCK_UNLOCKED(init_files.file_lock),
+	.resize_wait	= __WAIT_QUEUE_HEAD_INITIALIZER(init_files.resize_wait),
 };
 
 static unsigned int find_next_fd(struct fdtable *fdt, unsigned int start)
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] fs: initialize resize_wait wait queue of init task
  2017-06-14  0:27 ` [PATCH] fs: initialize resize_wait wait queue of init task Daeho Jeong
@ 2017-06-15 11:16   ` Al Viro
  0 siblings, 0 replies; 4+ messages in thread
From: Al Viro @ 2017-06-15 11:16 UTC (permalink / raw)
  To: Daeho Jeong; +Cc: edumazet, mguzik, linux-fsdevel

On Wed, Jun 14, 2017 at 09:27:21AM +0900, Daeho Jeong wrote:
> We don't initialize resize_wait of init task now and all the kernel
> threads share this uninitialized resize_wait wait queue because they
> are sharing the file table of init task. Therefore, when expanding
> this file table shared by the kernel threads, we encounter kernel panic
> by accessing the NULL resize_wait wait queue.

*shrug*

Not a problem, but kernel threads playing with init_files are seriously
asking for trouble.  It *is* shared and uncooperating threads playing
with shared descriptor table can fuck up very easily.  I can apply that,
but it might make more sense to restrict the use of that thing...

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] fs: initialize resize_wait wait queue of init task
  2017-05-16  6:40 ` Daeho Jeong
@ 2017-05-16 14:10   ` Eric Dumazet
  0 siblings, 0 replies; 4+ messages in thread
From: Eric Dumazet @ 2017-05-16 14:10 UTC (permalink / raw)
  To: Daeho Jeong; +Cc: mguzik, Al Viro, linux-fsdevel

On Mon, May 15, 2017 at 11:40 PM, Daeho Jeong <daeho.jeong@samsung.com> wrote:
> We don't initialize resize_wait of init task now and all the kernel
> threads share this uninitialized resize_wait wait queue because they
> are sharing the file table of init task. Therefore, when expanding
> this file table shared by the kernel threads, we encounter kernel panic
> by accessing the NULL resize_wait wait queue.
>
> Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
> Tested-by: Youngjin Gil <youngjin.gil@samsung.com>
> ---
>  fs/file.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/fs/file.c b/fs/file.c
> index ad6f094f2eff..74748c32e07a 100644
> --- a/fs/file.c
> +++ b/fs/file.c
> @@ -475,6 +475,7 @@ struct files_struct init_files = {
>                 .full_fds_bits  = init_files.full_fds_bits_init,
>         },
>         .file_lock      = __SPIN_LOCK_UNLOCKED(init_files.file_lock),
> +       .resize_wait    = __WAIT_QUEUE_HEAD_INITIALIZER(init_files.resize_wait),
>  };
>
>  static unsigned int find_next_fd(struct fdtable *fdt, unsigned int start)
> --
> 2.11.0
>

Acked-by: Eric Dumazet <edumazet@google.com>
Fixes: 8a81252b774b ("fs/file.c: don't acquire files->file_lock in
fd_install()")

I am curious, what kind of kernel threads are using file table ?
Thanks.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH] fs: initialize resize_wait wait queue of init task
       [not found] <CGME20170516064030epcas1p238af57ce4223442c821948621897d780@epcas1p2.samsung.com>
@ 2017-05-16  6:40 ` Daeho Jeong
  2017-05-16 14:10   ` Eric Dumazet
  0 siblings, 1 reply; 4+ messages in thread
From: Daeho Jeong @ 2017-05-16  6:40 UTC (permalink / raw)
  To: edumazet, mguzik, viro, linux-fsdevel; +Cc: Daeho Jeong

We don't initialize resize_wait of init task now and all the kernel
threads share this uninitialized resize_wait wait queue because they
are sharing the file table of init task. Therefore, when expanding
this file table shared by the kernel threads, we encounter kernel panic
by accessing the NULL resize_wait wait queue.

Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
Tested-by: Youngjin Gil <youngjin.gil@samsung.com>
---
 fs/file.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/file.c b/fs/file.c
index ad6f094f2eff..74748c32e07a 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -475,6 +475,7 @@ struct files_struct init_files = {
 		.full_fds_bits	= init_files.full_fds_bits_init,
 	},
 	.file_lock	= __SPIN_LOCK_UNLOCKED(init_files.file_lock),
+	.resize_wait	= __WAIT_QUEUE_HEAD_INITIALIZER(init_files.resize_wait),
 };
 
 static unsigned int find_next_fd(struct fdtable *fdt, unsigned int start)
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-06-15 11:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CGME20170614002719epcas5p3882aceef116f53781449010cc13f55e5@epcas5p3.samsung.com>
2017-06-14  0:27 ` [PATCH] fs: initialize resize_wait wait queue of init task Daeho Jeong
2017-06-15 11:16   ` Al Viro
     [not found] <CGME20170516064030epcas1p238af57ce4223442c821948621897d780@epcas1p2.samsung.com>
2017-05-16  6:40 ` Daeho Jeong
2017-05-16 14:10   ` Eric Dumazet

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.