Date:   Thu, 11 Nov 2021 18:13:42 +0200
From:   Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To:     huangbibo <huangbibo@uniontech.com>
Cc:     linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
        jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
        p.zabel@pengutronix.de
Subject: Re: [PATCH] i2c: designware: I2C unexpected interrupt handling will
 cause kernel panic
Message-ID: <YY1BNpKIbVVwf7F1@smile.fi.intel.com>
References: <20211111065759.7423-1-huangbibo@uniontech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20211111065759.7423-1-huangbibo@uniontech.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
Precedence: bulk

On Thu, Nov 11, 2021 at 02:57:59PM +0800, huangbibo wrote:
> I2C interrupts may be triggered unexpectedly,

> such as programs that directly access I2C registers,

Wow! What programs you are talking about? How comes they are doing this
weirdness in parallel with the OS running?

Can you elaborate, please?

> bus conflicts caused by hardware design defects, etc.
> These can cause null pointer reference errors and kernel panic.

-- 
With Best Regards,
Andy Shevchenko