linux-kernel - Re: [PATCH v1 0/2] serial: 8250

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YZuRnSaZz04KJIDk@smile.fi.intel.com>
Date:   Mon, 22 Nov 2021 14:48:29 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Jay Dolan <jay.dolan@...esio.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
        Jiri Slaby <jirislaby@...nel.org>
Subject: Re: [PATCH v1 0/2] serial: 8250_pci: Split Pericom driver

On Mon, Nov 22, 2021 at 02:47:20PM +0200, Andy Shevchenko wrote:
> On Thu, Nov 18, 2021 at 10:32:51PM -0800, Jay Dolan wrote:
> > On 11/17/21 6:57 AM, Andy Shevchenko wrote:
> > > Split Pericom driver to a separate module.
> > > While at it, re-enable high baud rates.
> > > 
> > > Jay, can you, please, test this on as many hardware as you have?
> 
> ...
> 
> > * Add in pericom_do_startup() because the UPF_MAGIC_MULTIPLIER doesn't
> > stick.
> 
> Can't find an evidence that this is the case. Can you recheck this (reading
> flags back via sysfs or so)? So, for v2 I'll leave my approach.

Otherwise how the other drivers which are using that flag survive? If it's
indeed an issue, it should be fixed on generic level.

-- 
With Best Regards,
Andy Shevchenko