linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wangzijie <wangzijie1@honor.com>
To: <akpm@linux-foundation.org>
Cc: <adobriyan@gmail.com>, <brauner@kernel.org>,
	<jirislaby@kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <sbrivio@redhat.com>,
	<spender@grsecurity.net>, <viro@zeniv.linux.org.uk>,
	<wangzijie1@honor.com>
Subject: Re: [PATCH] proc: fix type confusion in pde_set_flags()
Date: Fri, 5 Sep 2025 16:03:59 +0800	[thread overview]
Message-ID: <20250905080359.4063152-1-wangzijie1@honor.com> (raw)
In-Reply-To: <20250904155517.d623a254e8c25027c41e8e41@linux-foundation.org>

> On Thu, 4 Sep 2025 21:57:15 +0800 wangzijie <wangzijie1@honor.com> wrote:
> 
> > Commit 2ce3d282bd50 ("proc: fix missing pde_set_flags() for net proc files")
> > missed a key part in the definition of proc_dir_entry:
> > 
> > union {
> > 	const struct proc_ops *proc_ops;
> > 	const struct file_operations *proc_dir_ops;
> > };
> > 
> > So dereference of ->proc_ops assumes it is a proc_ops structure results in
> > type confusion and make NULL check for 'proc_ops' not work for proc dir.
> > 
> > Add !S_ISDIR(dp->mode) test before calling pde_set_flags() to fix it.
> > 
> > Fixes: 2ce3d282bd50 ("proc: fix missing pde_set_flags() for net proc files")
> 
> 2ce3d282bd50 had cc:stable, so I added cc:stable to this patch.
> 
> > Reported-by: Brad Spengler <spender@grsecurity.net>
> > Signed-off-by: wangzijie <wangzijie1@honor.com>
> 
> A link to Brad's report would be helpful please, if available.  We
> typically use Closes: for such things.

Closes: https://lore.kernel.org/all/20250903065758.3678537-1-wangzijie1@honor.com/

Thanks for reminder, I'm not sure if this link is appropriate.

      reply	other threads:[~2025-09-05  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 13:57 [PATCH] proc: fix type confusion in pde_set_flags() wangzijie
2025-09-04 22:55 ` Andrew Morton
2025-09-05  8:03   ` wangzijie [this message]

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=20250905080359.4063152-1-wangzijie1@honor.com \
    --to=wangzijie1@honor.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbrivio@redhat.com \
    --cc=spender@grsecurity.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).