From: gaoxu <gaoxu2@honor.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Barry Song <21cnbao@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: 回复: [PATCH v4] mm: Fix possible NULL pointer dereference in __swap_duplicate
Date: Wed, 19 Feb 2025 06:23:42 +0000 [thread overview]
Message-ID: <d9676b1355e84820aeeda18a1c77297a@honor.com> (raw)
In-Reply-To: <20250218200355.959a79bf9b6253772a95e782@linux-foundation.org>
>
> On Wed, 19 Feb 2025 15:28:26 +1300 Barry Song <21cnbao@gmail.com>
> wrote:
>
> > > The patch seems to only provide a workaround, but there are no more
> > > effective software solutions to handle the bit flips problem. This
> > > path will change the issue from a system crash to a process
> > > exception, thereby reducing the impact on the entire machine.
> > >
> > > Signed-off-by: gao xu <gaoxu2@honor.com>
> >
> > Regardless of whether the above statement is 100% accurate or whether
> > a bit-flip actually exists, providing this check still seems useful,
> > at least for defensive programming.
>
> I'm doubtful as well.
>
> How often has this crash been observed?
The probability of this issue occurring is approximately 1 in 500,000 per week.
prev parent reply other threads:[~2025-02-19 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 1:56 gaoxu
2025-02-19 2:28 ` Barry Song
2025-02-19 4:03 ` Andrew Morton
2025-02-19 6:23 ` gaoxu [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=d9676b1355e84820aeeda18a1c77297a@honor.com \
--to=gaoxu2@honor.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=yosry.ahmed@linux.dev \
/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