Re: Avoid speculative indirect calls in kernel

Alan Cox writes: > On Fri, 5 Jan 2018 01:54:13 +0100 (CET) > Thomas Gleixner wrote: > >> On Thu, 4 Jan 2018, Jon Masters wrote: >> > P.S. I've an internal document where I've been tracking "nice to haves" >> > for later, and one of them is whether

Re: Avoid speculative indirect calls in kernel

Alan Cox writes: > On Fri, 5 Jan 2018 01:54:13 +0100 (CET) > Thomas Gleixner wrote: > >> On Thu, 4 Jan 2018, Jon Masters wrote: >> > P.S. I've an internal document where I've been tracking "nice to haves" >> > for later, and one of them is whether it makes sense to tag binaries as >> >

Re: LSM conversion to static interface

Jan Engelhardt <[EMAIL PROTECTED]> writes: > Which reminded me of the TuxGuardian LSM[1] - another of the real-world > uses to meet Linus's criteria? ("had examples of their real-world use to > step forward and explain their use") > > In this specific project, LSM is used to collect up calls to

Re: LSM conversion to static interface

Jan Engelhardt [EMAIL PROTECTED] writes: Which reminded me of the TuxGuardian LSM[1] - another of the real-world uses to meet Linus's criteria? (had examples of their real-world use to step forward and explain their use) In this specific project, LSM is used to collect up calls to bind()

Re: [PATCH] sundance: PHY address form 0, only for device ID 0x0200 (IP100A) (20070605)

y <= 32 && phy_idx < MII_CNT; phy++) { I think this value can be put in driver_data. Attached patch is doing it, but I didn't test it. tree 602e0c2def631e82635b4f8aad762e69184af143 parent 5ecd3100e695228ac5e0ce0e325e252c0f11806f author Samir Bellabes <[EMAIL PROTECTED]>

Re: [PATCH] sundance: PHY address form 0, only for device ID 0x0200 (IP100A) (20070605)

can be put in driver_data. Attached patch is doing it, but I didn't test it. tree 602e0c2def631e82635b4f8aad762e69184af143 parent 5ecd3100e695228ac5e0ce0e325e252c0f11806f author Samir Bellabes [EMAIL PROTECTED] 1181086775 +0200 committer Samir Bellabes [EMAIL PROTECTED] 1181086775 +0200 Search PHY