The pull request you sent on Fri, 21 Dec 2018 12:42:25 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/87935eee57705e9b6df506c5df8b92d6a0b77a51
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 21 Dec 2018 12:42:43 -0800 (PST):
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc.git master
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6cafab50eea327e0d198cc9579a60440fc959756
Thank you!
--
Deet-doot-dot, I am a
On Fri, Dec 21, 2018 at 2:20 PM Joe Perches wrote:
>
> Using
>
> static inline bool str_has_prefix(const char *str, const char prefix[])
> {
> return !strncmp(str, prefix, strlen(prefix));
> }
>
> eliminates the strlen with gcc 4.8 (oldest I still have)
Ok, that looks like the right
Quoting Jerome Brunet (2018-12-21 08:03:29)
> On Mon, 2018-12-17 at 17:54 -0800, Stephen Boyd wrote:
> >
> > Ok. Thanks for the explanation. What should the framework do when the
> > parent is not known? Mark the clk as not an orphan but parent it to
> > NULL? That might work here.
>
> I don't
On Fri, 2018-12-21 at 16:08 -0500, Steven Rostedt wrote:
> On Fri, 21 Dec 2018 21:58:32 +0100
> Andreas Schwab wrote:
>
>
> > > Well, perhaps I can just remove the ending ones. I get paranoid with
> > > macro variables, and tend to over do it so that there's no question.
> >
> > Why not make
On 12/21/18 12:21 PM, Kirill A. Shutemov wrote:
> On Fri, Dec 21, 2018 at 10:28:25AM -0800, Mike Kravetz wrote:
>> On 12/21/18 2:28 AM, Kirill A. Shutemov wrote:
>>> On Tue, Dec 18, 2018 at 02:35:57PM -0800, Mike Kravetz wrote:
Instead of writing the required complicated code for this rare
On Fri, 14 Dec 2018, Vlastimil Babka wrote:
> > It would be interesting to know if anybody has tried using the per-zone
> > free_area's to determine migration targets and set a bit if it should be
> > considered a migration source or a migration target. If all pages for a
> > pageblock are
On Fri, 14 Dec 2018, Mel Gorman wrote:
> > In other words, I think there is a lot of potential stranding that occurs
> > for both scanners that could otherwise result in completely free
> > pageblocks. If there a single movable page present near the end of the
> > zone in an otherwise fully
On Fri, 2018-12-21 at 11:27 -0800, Paul Walmsley wrote:
> On Fri, 21 Dec 2018, Alistair Francis wrote:
>
> > When the MicroSemi driver does eventually go upstream this will
> > probably have to be discussed though as either the config or device
> > tree will need to be edited to ensure only one
On Fri, Dec 21, 2018 at 12:55 PM Steven Rostedt wrote:
>
> On Fri, 21 Dec 2018 12:41:17 -0800
> Linus Torvalds wrote:
>
> > Parentheses
>
> ?
Your patch actually had them, but in the body of your email you did
> #define have_prefix(str, prefix) ({ \
> const char *__pfx = (const char
On Fri 21 Dec 12:10 PST 2018, Evan Green wrote:
> In order to run an rmtfs daemon as an unprivileged user, that user would
> need access to the phys_addr and size sysfs attributes. Sharing these
> attributes with unprivileged users doesn't really leak anything
> sensitive, since if you have
Enable generic PCIe by default in the RISC-V defconfig, this allows us
to use QEMU's PCIe support out of the box.
Signed-off-by: Alistair Francis
---
v2:
- Keep the Xilinx PCIE enabled
arch/riscv/configs/defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git
On Fri 21 Dec 12:10 PST 2018, Evan Green wrote:
> Currently the qcom_rmtfs_memN devices are entirely invisible to the udev
> world.
> Add a class to the rmtfs device so that uevents fire when the device is added.
>
> Signed-off-by: Evan Green
I agree with Brian on the whitespace chances,
U.S. Customs and Border
Protection Acting Deputy
Commissioner
I am writing. in regards of your Package in our custody. with Mr. Jerry A.
Benson, A Diplomats from Global Agent Service was stopped at the border in
possession of the above mention metal box weight of about 25kg (Internal
On 12/21/2018 10:08 PM, Paul Burton wrote:
> Hi Marek,
>
> On Fri, Dec 21, 2018 at 09:08:28PM +0100, Marek Vasut wrote:
>> On 12/16/2018 11:28 PM, Paul Burton wrote:
>>> On Sun, Dec 16, 2018 at 11:01:18PM +0100, Marek Vasut wrote:
>>> I did suggest an alternative approach which would rename
On 12/21/18 9:44 AM, Tim Chen wrote:
Thomas,
Andi and I have made an update to our draft of the Spectre admin guide.
We may be out on Christmas vacation for a while. But we want to
send it out for everyone to take a look.
Can you add a section on how to compile out all mitigations that have
On Thu, 20 Dec 2018, Nicholas Mc Guire wrote:
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 871e41c..1c118d7 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -1258,7 +1258,7 @@ void __init vmalloc_init(void)
>
> /* Import existing vmlist entries. */
> for (tmp = vmlist;
On Fri, Dec 21, 2018 at 12:10:00PM -0800, Evan Green wrote:
> Currently the qcom_rmtfs_memN devices are entirely invisible to the udev
> world.
> Add a class to the rmtfs device so that uevents fire when the device is added.
>
> Signed-off-by: Evan Green
> ---
You've got some spurious
On 21/12/2018 21:43, Matthew Wilcox wrote:
On Fri, Dec 21, 2018 at 09:07:54PM +0200, Igor Stoppa wrote:
On 21/12/2018 20:41, Matthew Wilcox wrote:
On Fri, Dec 21, 2018 at 08:14:14PM +0200, Igor Stoppa wrote:
+static inline int memtst(void *p, int c, __kernel_size_t len)
I don't
Quoting Jorge Ramirez (2018-12-21 13:45:41)
> On 12/21/18 22:40, Stephen Boyd wrote:
> > Quoting Jorge Ramirez (2018-12-21 11:45:28)
> >> On 12/21/18 20:28, Bjorn Andersson wrote:
> >>> Perhaps there's a better way to define that this particular clock
> >>> hardware can change rate, but in this
proto is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
net/nfc/af_nfc.c:42 nfc_sock_create() warn: potential spectre issue 'proto_tab'
[w] (local cap)
Fix this by
swap_vma_readahead()'s comment is missed, just add it.
Cc: Huang Ying
Cc: Tim Chen
Cc: Minchan Kim
Signed-off-by: Yang Shi
---
mm/swap_state.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/mm/swap_state.c b/mm/swap_state.c
index 78d500e..dd8f698 100644
---
protocol is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
net/can/af_can.c:115 can_get_proto() warn: potential spectre issue 'proto_tab'
[w]
Fix this by sanitizing protocol
Swap readahead would read in a few pages regardless if the underlying
device is busy or not. It may incur long waiting time if the device is
congested, and it may also exacerbate the congestion.
Use inode_read_congested() to check if the underlying device is busy or
not like what file page
On 12/21/18 22:40, Stephen Boyd wrote:
Quoting Jorge Ramirez (2018-12-21 11:45:28)
On 12/21/18 20:28, Bjorn Andersson wrote:
Perhaps there's a better way to define that this particular clock
hardware can change rate, but in this implementation it must not?
the initialization for this
Quoting Taniya Das (2018-12-21 10:06:48)
> Add support to read the voltage look up table and populate OPP for all
> corresponding CPUS.
Yes, but why? Please specify the motivations in the commit text.
From: Enrico Granata
The ChromeOS EC has support for signaling to the host that
a single IRQ can serve multiple MKBP events.
Doing this serves an optimization purpose, as it minimizes the
number of round-trips into the interrupt handling machinery, and
it proves beneficial to sensor
From: Enrico Granata
The ChromeOS EC has support for signaling to the host that
a single IRQ can serve multiple MKBP events.
Doing this serves an optimization purpose, as it minimizes the
number of round-trips into the interrupt handling machinery, and
it proves beneficial to sensor
protocol is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
net/phonet/af_phonet.c:48 phonet_proto_get() warn: potential spectre issue
'proto_tab' [w] (local cap)
Fix this by
Quoting Jorge Ramirez (2018-12-21 11:45:28)
> On 12/21/18 20:28, Bjorn Andersson wrote:
> >
> > Perhaps there's a better way to define that this particular clock
> > hardware can change rate, but in this implementation it must not?
>
> the initialization for this particular PLL on this particular
Reword the NULL pointer dereference case to simply state that a NULL
pointer was dereferenced, i.e. drop "unable to handle" as that implies
that there are instances where the kernel actual does handle NULL
pointer dereferences, which is not true barring funky exception fixup.
For the non-NULL
Rework the messages printed for #PF oopses to display more detailed
information about the fault in human readable form and to avoid
conflicting messages and/or statements that may not always be accurate.
v3:
- Prepend a patch to reword the initial BUG message
- Add sample output in the
Linus pointed out that deciphering the raw #PF error code and printing
a more human readable message are two different things, and also that
printing the negative cases is mostly just noise[1]. For example, the
USER bit doesn't mean the fault originated in user code and stating
that an oops
The following changes since commit 8a034aad4892baf82f8c9082f969c5ebc1143a05:
clk: qcom: qcs404: Fix gpll0_out_main parent (2018-12-10 11:31:30 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-for-linus
for you to fetch
Hi Linus,
I picked this one up even if it is not exactly compiler-attributes.
I would like if you can take a look at the patch, please. The patch is harmless
for the kernel, but v4.19 was released with a few macros exposed to userspace
as the patch explains; which this removes, so it *could*
> > +static int tqmx86_create_platform_device(const struct dmi_system_id *id)
>
> This blows my mind.
>
> - The normal module_init() calls are initiated calling for a DMI scan
> - Then the DMI device init()s
> - You use the DMI init() to register this device as a platform device
> - Then
On Fri, Dec 21, 2018 at 01:07:21PM -0800, Matthew Wilcox wrote:
> On Fri, Dec 21, 2018 at 11:46:16PM +0300, Cyrill Gorcunov wrote:
> > Cast to unsigned char is needed in any case. And as far as I remember
> > we've been using this multiplication trick for a really long time
> > in x86 land. I'm
Hi Sasha,
On Thu, Dec 20, 2018 at 07:26:15PM +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 432c6bacbd0c MIPS: Use per-mm page to execute branch delay
> slot instructions.
>
> The bot has
On Fri, Dec 21, 2018 at 2:13 AM Sebastian Reichel wrote:
>
> From: Sebastian Reichel
>
> This driver has been superseded by the serdev based Bluetooth
> hci_ll driver, which is initialized from DT. All mainline users
> have been converted and this driver can be safely dropped.
There seems to be
Hi Marek,
On Fri, Dec 21, 2018 at 09:08:28PM +0100, Marek Vasut wrote:
> On 12/16/2018 11:28 PM, Paul Burton wrote:
> > On Sun, Dec 16, 2018 at 11:01:18PM +0100, Marek Vasut wrote:
> > I did suggest an alternative approach which would rename
> > serial8250_clear_fifos() and split it into
On Fri, 21 Dec 2018 21:58:32 +0100
Andreas Schwab wrote:
> > Well, perhaps I can just remove the ending ones. I get paranoid with
> > macro variables, and tend to over do it so that there's no question.
>
> Why not make it an inline function?
Matters if that removes the strlen(const)
On Fri, Dec 21, 2018 at 11:46:16PM +0300, Cyrill Gorcunov wrote:
> Cast to unsigned char is needed in any case. And as far as I remember
> we've been using this multiplication trick for a really long time
> in x86 land. I'm out of sources right now but it should be somewhere
> in assembly libs.
skb->sp doesn't exist anymore in the next-next tree, so mips defconfig
no longer builds. Use helper instead to reset the secpath.
Not even compile tested.
Cc: Greg Kroah-Hartman
Reported-by: Guenter Roeck
Fixes: 4165079ba328d ("net: switch secpath to use skb extension infrastructure")
On Fri, Dec 21, 2018 at 10:51 AM Dan Williams wrote:
>
> On Fri, Dec 21, 2018 at 10:44 AM Randy Dunlap wrote:
> >
> > On 12/21/18 12:32 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > News: there will be no linux-next release until Jan 2. Have a good break.
> > >
> > > Changes since
On Dez 21 2018, Steven Rostedt wrote:
> On Fri, 21 Dec 2018 12:46:47 -0800
> Joe Perches wrote:
>
>> > + * @str: The string to test
>> > + * @prefix: The string to see if @str starts with
>> > + *
>> > + * A common way to test a prefix of a string is to do:
>> > + * strncmp(str, prefix,
On Fri, 21 Dec 2018 12:46:47 -0800
Joe Perches wrote:
> I think all the underscores are unnecessary and confusing.
Here. I removed a beginning and ending underscore from each variable ;-)
-- Steve
diff --git a/include/linux/string.h b/include/linux/string.h
index 27d0482e5e05..7f8871f7
Hi Taniya,
On Fri, Dec 21, 2018 at 11:36:48PM +0530, Taniya Das wrote:
> Add support to read the voltage look up table and populate OPP for all
> corresponding CPUS.
>
> Signed-off-by: Taniya Das
> ---
> drivers/cpufreq/qcom-cpufreq-hw.c | 32 ++--
> 1 file changed,
Guenter Roeck wrote:
> mips:cavium_octeon_defconfig [4]
> git bisect bad 4165079ba328dd47262a2183049d3591f0a750b1
> # first bad commit: [4165079ba328dd47262a2183049d3591f0a750b1] net: switch
> secpath to use skb extension infrastructure
Indeed, sorry. staging/octeon needs a small fix.
On Fri, 21 Dec 2018 12:41:17 -0800
Linus Torvalds wrote:
> Parentheses
?
-- Steve
>
> On Fri, Dec 21, 2018, 12:35 Steven Rostedt
> > On Fri, 21 Dec 2018 12:01:48 -0800
> > Linus Torvalds wrote:
> >
> > > On Fri, Dec 21, 2018 at 11:40 AM Steven Rostedt
> > wrote:
> > > >
> > > > OK,
On Fri, 21 Dec 2018 12:46:47 -0800
Joe Perches wrote:
> > @@ -14,6 +14,28 @@ extern void *memdup_user(const void __user *, size_t);
> > extern void *vmemdup_user(const void __user *, size_t);
> > extern void *memdup_user_nul(const void __user *, size_t);
> >
> > +/**
> > + * have_prefix -
Hi Linus,
Please consider pulling this small fix for auxdisplay.
It is a bit late, and has been in linux-next for a couple of days only,
but it shouldn't break anything else further, so feel free to pick it
for either 4.20 or maybe afterwards.
Cheers,
Miguel
The following changes since commit
Remove warnings by selecting SND_HDA_INTEL_DSP_DETECTION_XYZ only when
SND_HDA_INTEL is part of the config.
Fixes: c337104b1a16 ('ALSA: HD-Audio: SKL+: abort probe if DSP is present and
Skylake driver selected')
Reported-by: Randy Dunlap
Signed-off-by: Pierre-Louis Bossart
---
flen is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
net/core/filter.c:1101 bpf_check_classic() warn: potential spectre issue
'filter' [w]
Fix this by sanitizing flen
On Fri, 2018-12-21 at 15:35 -0500, Steven Rostedt wrote:
> At first I thought this would have issues, but with a slight change...
>
> #define have_prefix(str, prefix) ({ \
> const char *__pfx = (const char *)prefix; \
>
>
> And the rest the same, it appears to work.
>
> Need the cast
On Fri, Dec 21, 2018 at 12:29:46PM -0800, Matthew Wilcox wrote:
> > >
> > > That's inefficient.
> > >
> > > pattern = (unsigned char)c;
> > > pattern |= pattern << 8;
> > > pattern |= pattern << 16;
> > > pattern |= pattern << 32;
> >
> > Won't
> >
> > pattern = 0x0101010101010101
Quoting Charles Keepax (2018-12-21 05:50:37)
> On Thu, Nov 29, 2018 at 11:53:51PM -0800, Stephen Boyd wrote:
> > Quoting Charles Keepax (2018-11-20 06:16:30)
>
> > > + break;
> > > + default:
> > > + dev_err(priv->dev, "Unknown Lochnagar type: %d\n",
> > >
Just some small fixes here and there, and a refcount leak in a serial
driver, nothing serious.
Please pull, thanks!
The following changes since commit cf76c364a1e1e5224af80edf70a1e3023e1fcf8c:
Merge tag 'scsi-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2018-12-05
Some more bug fixes have trickled in, we have:
1) Local MAC entries properly in mscc driver, from Allan W. Nielsen.
2) Eric Dumazet found some more of the typical "pskb_may_pull() -->
oops forgot to reload the header pointer" bugs in ipv6 tunnel
handling.
3) Bad SKB socket pointer in
On 12/21/18 12:02 PM, Randy Dunlap wrote:
On 12/21/18 12:32 AM, Stephen Rothwell wrote:
Hi all,
News: there will be no linux-next release until Jan 2. Have a good break.
Changes since 20181220:
on x86_64:
A new group of Kconfig "select"s is causing kconfig warnings:
WARNING: unmet
On 12/16/2018 11:28 PM, Paul Burton wrote:
> Hi Marek,
>
> On Sun, Dec 16, 2018 at 11:01:18PM +0100, Marek Vasut wrote:
> I did suggest an alternative approach which would rename
> serial8250_clear_fifos() and split it into 2 variants - one that
> disables FIFOs & one that does not,
On Fri, 21 Dec 2018 12:01:48 -0800
Linus Torvalds wrote:
> On Fri, Dec 21, 2018 at 11:40 AM Steven Rostedt wrote:
> >
> > OK, what about if we just use strlen() and say that this macro is not
> > safe for parameters with side effects.
>
> I think gcc follows simple assignments just fine, and
Quoting Derek Basehore (2018-12-20 16:31:00)
> It's not required to traverse the entire clk tree when the parents
> array contains a NULL value. You already have the parent clk_core
> pointer, so you can just compare the parent->name and parent_names[i]
> pointers.
Ok.
>
> In cases where clk
On Fri, Dec 21, 2018 at 11:05:46PM +0300, Cyrill Gorcunov wrote:
> On Fri, Dec 21, 2018 at 10:25:16AM -0800, Matthew Wilcox wrote:
> > On Fri, Dec 21, 2018 at 08:14:12PM +0200, Igor Stoppa wrote:
> > > +unsigned long __memset_user(void __user *addr, int c, unsigned long size)
> > > +{
> > > + long
On Fri, Nov 09, 2018 at 02:31:53PM +0300, Cyrill Gorcunov wrote:
> When showing timer's notify symbolic name make sure we never fetch a value
> sitting outside of the names array. Though the former issue displaying
> timer->it_sigev_notify has been fixed by Thomas in commit cef31d9af9082434,
>
Al Viro mentioned that there is probably a race condition
lurking in accesses of sk_tstamp on 32-bit machines.
sock->sk_tstamp is of type ktime_t which is always an s64.
On a 32 bit architecture, we might run into situations of
unsafe access as the access to the field becomes non atomic.
Use
On Fri, Dec 21, 2018 at 10:28:25AM -0800, Mike Kravetz wrote:
> On 12/21/18 2:28 AM, Kirill A. Shutemov wrote:
> > On Tue, Dec 18, 2018 at 02:35:57PM -0800, Mike Kravetz wrote:
> >> Instead of writing the required complicated code for this rare
> >> occurrence, just eliminate the race.
Currently the qcom_rmtfs_memN devices are entirely invisible to the udev world.
Add a class to the rmtfs device so that uevents fire when the device is added.
Signed-off-by: Evan Green
---
Changes in v2:
- Moved class registration/deregistration into init/exit routines (Brian)
In order to run an rmtfs daemon as an unprivileged user, that user would
need access to the phys_addr and size sysfs attributes. Sharing these
attributes with unprivileged users doesn't really leak anything
sensitive, since if you have access to physical memory, the jig is
up anyway.
Make those
This series contains minor fixes needed to better support running an
rmtfs daemon from an unprivileged process:
- Enable uevents on the child character device by adding a struct
class to the parent. I needed these so that I could change the
ownership of /dev/qcom_rmtfs_mem1, and drove myself
On Fri, Dec 21, 2018 at 10:25:16AM -0800, Matthew Wilcox wrote:
> On Fri, Dec 21, 2018 at 08:14:12PM +0200, Igor Stoppa wrote:
> > +unsigned long __memset_user(void __user *addr, int c, unsigned long size)
> > +{
> > + long __d0;
> > + unsigned long pattern = 0;
> > + int i;
> > +
> > +
On Thu, Dec 20, 2018 at 7:18 PM Sebastian Reichel wrote:
>
> From: Sebastian Reichel
>
> Add a node for the UART part of WiLink chip.
>
> Cc: Adam Ford
> Signed-off-by: Sebastian Reichel
> ---
> This is compile tested only!
I have tried this a few times, unfortunately, I cannot get the
On Fri, Dec 21, 2018 at 11:40 AM Steven Rostedt wrote:
>
> OK, what about if we just use strlen() and say that this macro is not
> safe for parameters with side effects.
I think gcc follows simple assignments just fine, and does the
optimized strlen() for them too.
So why not just do
Hi Shayenne,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on v4.20-rc7 next-20181221]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Fri, Dec 21, 2018 at 11:23:07AM -0800, Dhinakaran Pandiyan wrote:
> On Fri, 2018-12-21 at 10:23 -0700, Ross Zwisler wrote:
> > The following commit:
> >
> > commit 2bdd045e3a30 ("drm/i915/psr: Check if VBT says PSR can be
> > enabled.")
> >
> > added some code with no usable functionality.
When creating frame buffer, userspace may request to attach to a
previously allocated GEM object that is smaller than what GPU
requires. Validation must be done to prevent out-of-bound DMA,
which could not only corrupt memory but also reveal sensitive data.
This fix is not done in a common code
Userspace may request pitch alignment that is not supported by GPU.
Some requests 32, but GPU ignores it and uses default 64 when cpp is
4. If GEM object is allocated based on the smaller alignment, GPU
DMA will go out of bound.
For GPU that does frame buffer compression, DMA writing out of bound
On Fri, Dec 21, 2018 at 11:38:16AM -0800, Nadav Amit wrote:
> > On Dec 19, 2018, at 1:33 PM, Igor Stoppa wrote:
> >
> > +static inline void *wr_memset(void *p, int c, __kernel_size_t len)
> > +{
> > + return __wr_op((unsigned long)p, (unsigned long)c, len, WR_MEMSET);
> > +}
>
> What do you
On 12/21/18 20:28, Bjorn Andersson wrote:
On Fri 21 Dec 09:58 PST 2018, Taniya Das wrote:
Hello,
On 12/21/2018 6:06 PM, Jorge Ramirez wrote:
On 12/21/18 12:19, Taniya Das wrote:
On 12/17/2018 3:16 PM, Jorge Ramirez-Ortiz wrote:
Limit the GPLL0_AO_OUT_MAIN operating frequency as per its
On Fri, Dec 21, 2018 at 09:07:54PM +0200, Igor Stoppa wrote:
> On 21/12/2018 20:41, Matthew Wilcox wrote:
> > On Fri, Dec 21, 2018 at 08:14:14PM +0200, Igor Stoppa wrote:
> > > +static inline int memtst(void *p, int c, __kernel_size_t len)
> >
> > I don't understand why you're verifying that
On Fri, 21 Dec 2018 10:51:29 -0800
Linus Torvalds wrote:
> On Fri, Dec 21, 2018 at 9:57 AM Steven Rostedt wrote:
> >
> > I figured the best thing to do is to create a helper macro and place it
> > into include/linux/string.h. And go around and fix all the open coded
> > versions of it later.
>
On Fri, Dec 21, 2018 at 10:07:26AM +0100, Michel Dänzer wrote:
> On 2018-12-21 4:10 a.m., Yu Zhao wrote:
> > Userspace may request pitch alignment that is not supported by GPU.
> > Some requests 32, but GPU ignores it and uses default 64 when cpp is
> > 4. If GEM object is allocated based on the
> On Dec 19, 2018, at 1:33 PM, Igor Stoppa wrote:
>
> +static inline void *wr_memset(void *p, int c, __kernel_size_t len)
> +{
> + return __wr_op((unsigned long)p, (unsigned long)c, len, WR_MEMSET);
> +}
What do you think about doing something like:
#define __wr
FYI, we noticed the following commit (built with gcc-7):
commit: 641fb0efbff063ed57f108c2eb4a4d26dbd5badd ("iommu/of: Don't call
iommu_ops->add_device directly")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: trinity
with following parameters:
The pull request you sent on Fri, 21 Dec 2018 14:09:02 +0100:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5092adb2272e1760030a889aa4a3e9cf1d5f74b5
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 21 Dec 2018 01:12:58 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0b517333721c1b7a740e54b1cbe78a14884d51e7
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 21 Dec 2018 13:25:45 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/70ad6368e878857db315788dab36817aa992c86a
Thank you!
--
Deet-doot-dot, I am
On Fri, Dec 21, 2018 at 06:26:23PM +0100, Ard Biesheuvel wrote:
> On Fri, 21 Dec 2018 at 18:13, Borislav Petkov wrote:
> >
> > On Fri, Dec 21, 2018 at 06:02:29PM +0100, Ard Biesheuvel wrote:
> > > As far as I can tell, the SGI x86 UV platforms still rely on this, so
> > > we're stuck with it for
The pull request you sent on Fri, 21 Dec 2018 13:30:15 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> locking-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d5fa080d4ceaa8fec0fb28e27c7447caf4b4d22b
Thank you!
--
The pull request you sent on Fri, 21 Dec 2018 13:34:53 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e572fa0e840154d33a69622af030dda551eee606
Thank you!
--
Deet-doot-dot,
The pull request you sent on Fri, 21 Dec 2018 09:59:10 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
> tags/gpio-v4.20-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bc380733a5e77ccc3b4d4622595e42f1b0902d66
Thank you!
--
On Fri, 21 Dec 2018 10:24:14 -0800 (PST)
David Miller wrote:
> From: Steven Rostedt
> Date: Fri, 21 Dec 2018 12:56:24 -0500
>
> > From: "Steven Rostedt (VMware)"
> >
> > The structure of the ret_stack array on the task struct is going to
> > change, and accessing it directly via the
Big endian machines (at least the one I have access to) cannot mount
f2fs filesystems anymore.
This is with Linux 4.14.89 but I suspect that 4.9.144 (and later) is
affected as well.
commit 0cfe75c5b01199 ("f2fs: enhance sanity_check_raw_super() to avoid
potential overflows") treats the
Treat "block_count" from struct f2fs_super_block as 64-bit little endian
value in sanity_check_raw_super() because struct f2fs_super_block
declares "block_count" as "__le64".
This fixes a bug where the superblock validation fails on big endian
devices with the following error:
F2FS-fs (sda1):
On Fri 21 Dec 09:58 PST 2018, Taniya Das wrote:
> Hello,
>
> On 12/21/2018 6:06 PM, Jorge Ramirez wrote:
> > On 12/21/18 12:19, Taniya Das wrote:
> > >
> > >
> > > On 12/17/2018 3:16 PM, Jorge Ramirez-Ortiz wrote:
> > > > Limit the GPLL0_AO_OUT_MAIN operating frequency as per its hardware
> >
On Fri, 21 Dec 2018, Alistair Francis wrote:
> When the MicroSemi driver does eventually go upstream this will
> probably have to be discussed though as either the config or device
> tree will need to be edited to ensure only one PCIe device is present.
The right way to do that is to have two
On Fri, Dec 21, 2018 at 12:32 AM kernel test robot
wrote:
>
> FYI, we noticed commit df2052cc9221 ("bochs: convert to
> drm_fb_helper_fbdev_setup/teardown") caused
>
> [ 487.591733] WARNING: CPU: 0 PID: 1 at
> drivers/gpu/drm/drm_mode_config.c:478 drm_mode_config_cleanup+0x270/0x290
Ok, this
From: Yangtao Li
Date: Wed, 12 Dec 2018 11:01:45 -0500
> The function of_find_node_by_path() acquires a reference to the node
> returned by it and that reference needs to be dropped by its caller.
>
> su_get_type() doesn't do that. The match node are used as an identifier
> to compare against
From: ndesaulni...@google.com
Date: Mon, 10 Dec 2018 14:35:13 -0800
> GNU linker's -z common-page-size's default value is based on the target
> architecture. arch/sparc/vdso/Makefile sets it to the architecture
> default, which is implicit and redundant. Drop it.
>
> Link:
>
From: Corentin Labbe
Date: Tue, 11 Dec 2018 12:11:09 +
> While checking boot log from SPARC qemu, I saw that the "ARCH: sunxx"
> information was split on two different line.
> This patchs merge both line together.
> In the meantime, thoses information need to be printed via pr_info
> since
On Fri, 2018-12-21 at 10:23 -0700, Ross Zwisler wrote:
> The following commit:
>
> commit 2bdd045e3a30 ("drm/i915/psr: Check if VBT says PSR can be
> enabled.")
>
> added some code with no usable functionality. Regardless of how the
> psr
> default is set up in the BDB_DRIVER_FEATURES section,
101 - 200 of 729 matches
Mail list logo
