Am Fr., 12. Nov. 2021 um 11:43 Uhr schrieb Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>: > > On Fri, Nov 12, 2021 at 10:09:14AM +0000, Richard Hughes wrote: > > On Fri, 12 Nov 2021 at 06:52, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > Why don't we just export these areas to userspace and let the decoding > > > of them happen there? > > > > Unless I'm missing something, the patch from Hans-Gert does just that: > > exposing the IFD BIOS partition that encloses the various EFI file > > volumes. > > But it is not tied into the EFI subsystem at all, binding only to those > resources. It does not do anything with any efi symbol or access > control. > > Again, that's my primary complaint here, the driver HAS to be able to > tell the kernel what resource it wants to bind to and control, right now > it just "assumes" that it can have access to a chunk of memory without > any notification or checks at all, which will cause problems on systems > that do not follow that assumption. > > So while you all are arguing over oddities, the main complaint here of > "this driver is not ok as-is" seems to keep being ignored for some odd > reason. No, no, at least I am not ignoring it. I am aware of that and I was planning to fix the broken parts since the start of the discussion. Sorry for the miscommunication here. > > I'm going to just ignore this thread now and wait for a new patch to > review. That's the plan and I'd be happy if we don't have to discuss it further right now. > > thanks, > > greg k-h Hans-Gert
