Re: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: wangzijie <wangzijie1@xxxxxxxxx>
Subject: Re: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Thu, 5 Jun 2025 14:44:15 -0700
Cc: <rick.p.edgecombe@xxxxxxxxx>, <ast@xxxxxxxxxx>, <adobriyan@xxxxxxxxx>, <kirill.shutemov@xxxxxxxxxxxxxxx>, <linux-fsdevel@xxxxxxxxxxxxxxx>
In-reply-to: <20250605065252.900317-1-wangzijie1@honor.com>

On Thu, 5 Jun 2025 14:52:52 +0800 wangzijie <wangzijie1@xxxxxxxxx> wrote:

> Clearing FMODE_LSEEK flag should not rely on whether proc_open ops exists,

Why is this?

> fix it.

What are the consequences of the fix?  Is there presently some kernel
misbehavior?

Follow-Ups:
- Re: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
  - From: Al Viro

References:
- [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
  - From: wangzijie

Prev by Date: Re: [PATCH 2/3] userfaultfd: prevent unregistering VMAs through a different userfaultfd
Next by Date: Re: [PATCH] fs/xattr.c: fix simple_xattr_list()
Previous by thread: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
Next by thread: Re: [PATCH] proc: clear FMODE_LSEEK flag correctly for permanent pde
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux