> On July 29, 2019 at 2:00 AM Daniel Axtens wrote:
>
> Would you be able to send a v2 with these changes? (that is, not purging
> breakpoints when entering integrity mode)
>
Just sent out a v3 with that change among a few others and a rebase.
Thanks,
Chris R.
Xmon should be either fully or partially disabled depending on the
kernel lockdown state.
Put xmon into read-only mode for lockdown=integrity and completely
disable xmon when lockdown=confidentiality. Xmon checks the lockdown
state and takes appropriate action:
(1) during xmon_setup to prevent e
On Sat, 03 Aug 2019 12:30:24 +0200,
Christoph Hellwig wrote:
>
> On Fri, Aug 02, 2019 at 10:24:02AM +0200, Takashi Iwai wrote:
> > I wasn't careful enough to look at that change, sorry.
> >
> > The code there tries to check whether dma_mmap_coherent() would always
> > fail on some platforms. The
On Fri, Aug 02, 2019 at 10:24:02AM +0200, Takashi Iwai wrote:
> I wasn't careful enough to look at that change, sorry.
>
> The code there tries to check whether dma_mmap_coherent() would always
> fail on some platforms. Then the driver clears the mmap capability
> flag at the device open time and
