From: Al Viro <viro@zeniv.linux.org.uk>
To: cheung wall <zzqq0103.hey@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: “BUG: unable to handle kernel paging request in anon_inode_getfile” in Linux Kenrel Version 2.6.32
Date: Mon, 2 Dec 2024 04:39:52 +0000 [thread overview]
Message-ID: <20241202043952.GP3387508@ZenIV> (raw)
In-Reply-To: <CAKHoSAtp6Eu3HoUvdGuaHxt21zoHkVWmmGrRK9mw2T+-r-fEYw@mail.gmail.com>
On Mon, Dec 02, 2024 at 12:31:22PM +0800, cheung wall wrote:
> Hello,
>
> I am writing to report a potential vulnerability identified in the
> Linux Kernel version 2.6.32, specifically on the PowerPC architecture.
> This issue was discovered using our custom vulnerability discovery
> tool.
Sorry, I'd need to rebuild the memories of the state of kernel 15 years
ago to do anything useful with it (such as, say, check if it's something
covered by subsequent changes). As it is, you are rapidly training
everybody to ignore your postings; presumably that is not the desired
effect...
prev parent reply other threads:[~2024-12-02 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 4:31 “BUG: unable to handle kernel paging request in anon_inode_getfile” in Linux Kenrel Version 2.6.32 cheung wall
2024-12-02 4:39 ` Al Viro [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=20241202043952.GP3387508@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zzqq0103.hey@gmail.com \
/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